Wireless relay backhaul selection in a data communication network

ABSTRACT

A wireless relay controls backhaul in a data communication network. Relay user equipment attaches to a wireless base station coupled to a data network core and receives a first backhaul connection. An Ethernet switch attaches to a network gateway coupled to the data network core and establishes a second backhaul connection. The relay base station receives status data for the first backhaul connection through the wireless base station. The relay base station exchanges wireless user data with served user equipment. The relay base station selects one of the backhaul connections for the user data based on the status data of the first backhaul connection and exchanges the user data with the data network core over the selected one of the backhaul connections. The relay base station may receive and use status data for the second backhaul connection or the user data media type to select backhaul connections.

TECHNICAL BACKGROUND

Wireless communication networks exchange user data between communicationdevices to facilitate various data services, like internet access, voicecalling, media streaming, data messaging, and the like. Wirelesscommunication networks allow users to move about as they communicate. Apopular form of wireless communication network is Long Term Evolution(LTE). Wireless relays are used to extend the coverage area of wirelessnetworks including LTE networks.

The wireless relays serve user devices and exchange user data withwireless base stations or another network gateway. In LTE networks,femtocell relays and picocell relays exchange user data and usersignaling over the air between User Equipment (UE) and eNodeBs. Thewireless relays also exchange data and signaling between the UEs and aSecure Gateway (Se-GW) over a Local Area Network/Wide Area Network(LAN/WAN). These wireless relay communications use various combinationsof Ethernet, Data over Cable System Interface Specification (DOCSIS),Wave Division Multiplex (WDM), Wireless Fidelity (WIFI), Long TermEvolution (LTE), WIFI/LTE Aggregation (LWA), or some other datacommunication protocol.

The typical wireless relay automatically establishes a backhaulconnection upon power up. If the backhaul connection goes down, then thewireless relay loses network connectivity. To provide reliability, somewireless relays have dual backhaul connections. For example, some WIFIhotspots have dual WIFI backhaul links to separate WIFI aggregationnodes. Smart phones that offer tethering to other devices offer dualbackhaul over both a WIFI/DOCSIS connection and an LTE link.

Unfortunately, wireless relays are not effective when selecting backhaulconnections for individual UEs. Both the data and the intelligence toperform more effective backhaul selection in wireless relays is lacking.

TECHNICAL OVERVIEW

A wireless relay controls backhaul in a data communication network.Relay user equipment attaches to a wireless base station coupled to adata network core and receives a first backhaul connection. An Ethernetswitch attaches to a network gateway coupled to the data network coreand establishes a second backhaul connection. The relay base stationreceives status data for the first backhaul connection through thewireless base station. The relay base station exchanges wireless userdata with served user equipment. The relay base station selects one ofthe backhaul connections for the user data based on the status data ofthe first backhaul connection and exchanges the user data with the datanetwork core over the selected one of the backhaul connections. Therelay base station may receive and use status data for the secondbackhaul connection or the user data media type to select backhaulconnections.

DESCRIPTION OF THE DRAWINGS

FIGS. 1-3 illustrates a data communication network to select backhaulconnections for data and media services that are delivered over awireless relay.

FIG. 4 illustrates a Long Term Evolution (LTE) data communication systemhaving a Relay Gateway (R-GW) to proxy signaling for picocell relays andfemtocell relays.

FIGS. 5-17 illustrate a variant of the LTE data communication systemthat uses Proxy Mobile Internet Protocol (PMIP) Generic RoutingEncapsulation (GRE) tunnels between Local Serving Gateways (L-SGWs) inthe relays and macro Packet Data Security Gateways (P-GWs).

FIGS. 18-28 illustrate a variant of the LTE data communication systemthat uses SGi tunnels between Local Packet Data Network Gateways(L-PGWs) in the relays and macro P-GWs.

DETAILED DESCRIPTION

FIGS. 1-3 illustrates data communication network 100 to select backhaulconnections for data and media services that are delivered over wirelessrelay 110. Referring to FIG. 1, data communication network 100 comprisesUser Equipment (UE) 101, wireless relay 110, wireless base station 121,network gateway 122, and data network core 130. Wireless relay 110comprises relay base station 111, Ethernet switch 112, and relay UE 113.UE 101 might be a computer, phone, media player, machine transceiver,and the like.

The dotted lines between relay base station 111 and data network core130 represent dual backhaul options. The first backhaul connection (BH1)traverses Ethernet switch 112, relay UE 113, and wireless base station121. BH1 uses Ethernet, Long Term Evolution (LTE), Wireless Fidelity/LTEAggregation (LWA), or some other wireless communication protocol. BH1 iscompressed in between relay UE 113 and wireless base station 121. Foruser data, relay UE 113 and wireless base station 121 may use RobustHeader Compression (RoHC). The second backhaul connection (BH2)traverses Ethernet switch 112 and network gateway 122. BH2 usesEthernet, Data over Cable System Interface Specification (DOCSIS), WaveDivision Multiplex (WDM), Time Division Multiplex (TDM), or some otherdata communication protocol.

In operation, relay UE 113 attaches to wireless base station 121.Wireless base station 121 might be a macrocell eNodeB that is coupled todata network core 130. In response to attachment, relay UE 113 receivesBH1 through wireless base station 121 to data network core 130. Relay UE113 extends BH1 to relay base station 111. Relay UE 113 receives statusdata for BH1 and transfers the BH1 status data to relay base station 111over Ethernet switch 112.

Ethernet switch 112 attaches to network gateway 122. Network gateway 122might be a Secure Gateway (Se-GW) that is coupled to data network core130. In response to attachment, Ethernet switch 112 receives BH2 throughnetwork gateway to data network core 130. Ethernet switch 112 extendsBH2 to relay base station 111. Ethernet switch 112 receives BH2 statusdata through network gateway 130 and transfers the BH2 status data torelay base station 111.

Relay base station 111 exchanges wireless user data with served UE 101.Relay base station 111 selects BH1 or BH2 for the user data based on theBH1 status data and exchanges the user data with data network core 130over the selected BH1 or BH2. If BH1 has capacity, then BH1 is typicallyused—especially for compressed media streams like voice and video. IfBH1 does not have capacity, then BH2 is typically used—especially forgeneric internet data like web browsing.

Relay base station 111 may receive the BH1 status data and/or the BH2status data over BH1 and/or BH2. In some examples, relay base station111 establishes signaling links over BH1 and/or BH2. The signaling linksmay comprise X2 links between relay base station 111 and wireless basestation 121 over BH1 or BH2. The signaling links may comprise an S1-MMElinks between relay base station 111 and a Mobility Management Entity(MME) in data network core 130 over BH1 or BH2. The S1-MME link may usemulti-home Stream Control Transmission Protocol (SCTP).

The network elements of data communication network 100 (110, 111-113,121-122, and 130) comprise computer and communication platforms thatinclude data Input/Output (I/O) transceivers, digital processingcircuitry, data storage memories, and various software components. Thecommunication bearers of data communication network 100 comprise datanetworking media, nodes, and protocols that transport user data andnetwork signaling. The media comprises metal, glass, air, and/or space.The nodes comprise modems, routers, and firewalls. The protocolscomprise LTE, WiFi, Ethernet, IP, PMIP, DOCSIS, WDM, and TDM.

FIG. 2 illustrates the operation of data communication network 100 toselect backhaul connections for user data services that are deliveredover wireless relay 110. Relay UE 113 attaches to wireless base station121. Wireless base station 121 extends the attachment to data networkcore 130. In response to attachment, relay UE 113 receives BH1. BH1might be a default data bearer in an LTE network. Data network core 130transfers BH1 status data to relay UE 113 over wireless base station121, and relay UE 113 transfers the BH1 status data to relay basestation 111. The status data from network core 130 may be delivered overa Non-Access Stratum (NAS) link to relay UE 113 or an S1-MME link torelay base station 111. Wireless base station 121 may also transfer BH1status data to relay base station 111. Wireless base station 121 maydeliver this BH1 status data over an X2 link to relay base station 111.

Ethernet switch 112 attaches to network gateway 122. Network gateway 122extends the attachment to data network core 130. In response toattachment, Ethernet switch 112 receives BH2. BH2 might be a publicinternet connection to an LTE network. Data network core 130 transfersBH2 status data to Ethernet switch 112 over network gateway 122, andEthernet switch 112 transfers the BH2 status data to relay base station111.

Relay base station 111 exchanges wireless user data with served UE 101.Relay base station 111 selects BH1 for the user data based on the BH1status data. Relay base station 111 exchanges the user data with datanetwork core 130 over the selected BH1 that traverses Ethernet switch112, relay UE 113, and wireless base station 120. Relay base station 111uses BH1 if it has capacity. If the BH1 status data indicates that BH1capacity falls below a threshold, then, Relay base station 111 selectsBH2.

FIG. 3 illustrates the operation of data communication network 100 toselect backhaul connections for media services that are delivered overwireless relay 110. Relay UE 113 attaches to wireless base station 121.Wireless base station 121 extends the attachment to data network core130. In response to attachment, relay UE 113 receives BH1. BH1 comprisesa data bearer in an LTE network that uses RoHC between relay UE 113 andwireless base station 121. Data network core 130 transfers BH1 statusdata to relay UE 113 over wireless base station 121, and relay UE 113transfers the BH1 status data to relay base station 111. The status datafrom network core 130 may be delivered over a Non-Access Stratum (NAS)link to relay UE 113 or an S1-MME link to relay base station 111.Wireless base station 121 may also transfer BH1 status data to relaybase station 111 over an X2 link.

Ethernet switch 112 attaches to network gateway 122. Network gateway 122extends the attachment to data network core 130. In response toattachment, Ethernet switch 112 receives BH2. BH2 is a public internetconnection to an LTE network. Data network core 130 transfers BH2 statusdata to Ethernet switch 112 over network gateway 122, and Ethernetswitch 112 transfers the BH2 status data to relay base station 111.

Relay base station 111 exchanges wireless signaling and voice data withserved UE 101. Relay base station 111 selects BH1 for the voice databased on the BH1 status data showing adequate capacity. Relay basestation 111 exchanges the voice data with data network core 130 over theselected BH1 that traverses Ethernet switch 112, relay UE 113, andwireless base station 120. If the BH1 status data indicates that BH1capacity falls below a threshold, then relay base station 111 may useBH2 for the voice data.

Relay base station 111 exchanges wireless signaling and internet datawith served UE 101. Relay base station 111 selects BH2 for the internetdata based on the BH2 status data showing adequate credits under atariff. Relay base station 111 exchanges the internet data with datanetwork core 130 over the selected BH2 that traverses Ethernet switch112 and network gateway 122. If the BH2 status data indicates that BH2credits falls below a threshold, then relay base station 111 may use BH1for the internet data. Thus, the BH2 status data would include availabledata transfer amounts under the tariff or indications of when and whennot to use BH2 based on actual data usage against a tariff threshold.

Media types other than voice could be handled in a similar manner. Forexample, uncompressed media types may be transported over BH2 whilecompressed media types are transported over BH1. Audio and videostreaming services could be identified implement a service-specificbackhaul logic in wireless relay 110. Wireless capacity thresholds andnetwork tariffs thresholds could be used by wireless relay 110 to moveindividual and specific media types back and forth between BH1 and BH2.

FIG. 4 illustrates Long Term Evolution (LTE) communication system 400that comprises Relay Gateway (R-GW) 437 to proxy LTE signaling forfemtocell relay 410 and picocell relay 420. LTE communication system 400comprises: User Equipment (UEs) 401-403, femtocell relay 410, picocellrelay 420, macrocell eNodeB 421, Serving Gateway (S-GW) 431, MobilityManagement Entity (MME) 432, Home Subscriber System (HSS) 433, PacketData Network Gateway (P-GW) 434, Policy and Charging Rules Function(PCRF) 435, Accounting system (ACCT) 436, R-GW 437, Security Gateway(Se-GW) 438, and routers 451-453. Femtocell relay 410 comprises UE 404and eNodeB 423. Picocell relay 420 comprises UE 405 and eNodeB 422.

Femtocell relay 410 is coupled to router 451 over a Local Area Network(LAN) such as an Ethernet LAN. Router 451 is coupled to router 453 overa Wide Area Network (WAN) such as a Data Over Cable Service InformationSpecification (DOCSIS) system, Time Division Multiplex (TDM), WaveDivision Multiplexing (WDM), Ethernet, or some other data network.Picocell relay 420 is coupled to router 452 over a LAN. Router 452 iscoupled to router 453 over a WAN. Router 453 is coupled to Se-GW 438.The number and configuration of routers illustrated is representativeand may vary.

To attract UEs using LTE, eNodeBs 421-423 broadcast various Public LandMobile Network Identifiers (PLMN IDs). UEs 401-405 receive the PLMNbroadcasts and identify their desired LTE network during LTE attachmentusing the broadcast PLMN IDs. Referring to the circled number one onFIG. 4, macrocell eNodeB 421 broadcasts a PLMN ID of MACRO RELAY toattract relays like femtocell relay 410 and picocell relay 420.Macrocell eNodeB 421 broadcasts PLMN IDs for MACRO UE DATA and MACRO UEVOLTE to attract UEs like UE 401. Likewise, picocell eNodeB 422broadcasts PLMN IDs for PICO UE DATA, PICO UE VOLTE, and PICO RELAY.Femtocell eNodeB 421 broadcasts PLMN IDs for FEMTO UE DATA and FEMTO UEVOLTE. A PLMN ID is typically associated with one or more Access PointNames (APNS) that are selected by MME 432 and HSS 433 when a UE attachesusing that PLMN ID.

To attract UEs using WiFi, eNodeBs 422-423 also broadcast various WiFiService Set Identifiers (SSIDs). UEs 402-404 receive the SSID broadcastsand identify their desired WiFi network during WiFi attachment using thebroadcast SSIDs. For example, a picocell SSID might be as simple as“PICO 420” or be more complex like “PICO 420 RELAY”, “PICO 420 UE DATA”,or “PICO 420 UE VOLTE.” Using Packet Data Convergence Protocol (PDCP),eNodeBs 422-423 convert between the Wifi data and the LTE data.

UEs 402-404 and eNodeBs 422-423 exchange wireless data communicationsusing LTE/WiFi Aggregation (LWA). With LWA, eNodeBs 422-423 expose bothWiFi and LTE access interfaces to UEs 402-404 over unlicensed spectrumat 2.4 GHz, 5 GHz, or some other band. In addition, eNodeBs 422-423expose LTE access interfaces to UEs 402-404 over licensed spectrumbetween 0.3 GHz-3 GHz or some other band. Thus, UEs 402-404 may use LTEor WiFi over licensed or unlicensed spectrum. UE 404 may use LWA toexchange compressed user data and LTE signaling with eNodeB 422 by usingWiFi over unlicensed spectrum. UE 405 may use LTE to exchange compresseduser data and LTE signaling with eNodeB 421—perhaps over unlicensedspectrum.

To facilitate LWA, UEs 402-404 and eNodeBs 422-423 perform PDCPaggregation for the WiFi user data and signaling. The LTE PDCP layerhandles user data and LTE signaling between the LTE IP layer and the LTERadio Link Control (RLC) layer. The LTE RLC layer handles user data andsignaling between the PDCP layer and the LTE Medium Access Control (MAC)Layer. With PDCP aggregation, an LTE/WiFi RLC layer is adapted toexchange user data between the WiFi MAC layer and the LTE PDCP layer.The LTE/WiFi RLC layer interworks between WiFi and LTE.

UEs 401-405 and eNodeBs 421-423 perform compression/decompression on theuser data and signaling to wirelessly exchange compressed user data andLTE signaling over the air. The PDCP layers in UEs 401-405 and ineNodeBs 421-423 perform user data compression/decompression using RobustHeader Compression (RoHC) at the Real-time Transfer Protocol (RTP)layer, User Datagram Protocol (UDP) layer, and Internet Protocol (IP)layer. The PDCP layers in UEs 401-405 and in eNodeBs 421-423 perform LTEsignaling compression/decompression using general compression at theUser Datagram Protocol (UDP) layer and the Internet Protocol (IP) layer.

UEs 402-404 exchange WiFi and/or LTE data with eNodeBs 422-423. Relays410 and 420 have the option of exchanging the user data with theInternet over the LAN/WAN using their Local Internet Protocol Access(LIPA) interfaces. Relays 410 and 420 may also exchange their user datawith P-GW 434 over the backhaul provided by the LWA/LTE interfaces. Inaddition, Relays 410 and 420 may exchange the user data with P-GW 434over the backhaul provided by the LAN/WAN interfaces.

To backhaul their user data, eNodeBs 421-423 generate S1-U GeneralPacket Radio Service Transfer Protocol User (GTP-U) data tunnels totheir respective S-GWs. The S-GWs terminate these S1-U GTP-U datatunnels from eNodeBs 421-423. In femtocell relay 410, a Local S-GW(L-SGW) terminates the S1-U GTP-U tunnel from eNodeB 423. UE 404 andeNodeB 422 may exchange this user data using LWA/LTE and RoHC. Inpicocell relay 420, an L-SGW terminates the S1-U GTP-U tunnel fromeNodeB 422. UE 405 and eNodeB 421 may exchange the user data using LTEand RoHC.

To service the user data, relays 410 and 420 generate LTE signaling(S1-MME, S11, S15, X2, and Gy/Gz). Relays 410 and 420 exchange the LTEsignaling with R-GW 437 over the backhaul provided by the LWA/LTEinterfaces or the backhaul provided by the LAN/WAN interfaces. R-GW 437exchanges the LTE signaling with eNodeB 421 (X2), MME 432 (S1-MME andS11), P-GW 434 (PMIP), PCRF 435 (S15), and ACCT 436 (Gz/Gy). At themacro layer, eNodeB 421 and MME 432 exchange S1-MME signaling. S-GW 431and MME 432 exchange S11 signaling. P-GW 434 and PCRF 435 exchange Gxsignaling. P-GW 434 and ACCT 436 exchange Gz/Gy signaling. Macro eNodeB421 and S-GW 431 exchange S1-U data. S-GW 431 and P-GW 434 exchange S5data. P-GW 434 exchanges SGi data with various systems including R-GW437.

FIGS. 5-17 illustrate a variant of the LTE data communication system 400that uses Proxy Mobile Internet Protocol (PMIP) Generic RoutingEncapsulation (GRE) tunnels between Local Serving Gateways (L-SGWs) inrelays 410 and 420 and macro P-GW 434. The use of the PMIP GRE tunnelsfacilitates UE IP address continuity when UE 403 is mobile. Referring toFIG. 5, a Local Mobility Anchor (LMA) in P-GW 434 is coupled to a MobileAccess Gateway (MAG) in the Local S-GW (L-SGW) of femtocell relay 410.

UE 403 has a data bearer and a signaling bearer with femtocell relay410. The L-SGW in femtocell relay 410 may exchange some of this userdata with the Internet over routers 451 and 453 in a LIPA data service.The MAG in femtocell relay 410 may exchange some of the user data withthe LMA in P-GW 434 over a PMIP GRE tunnel through picocell relay 420,eNodeB 421, and S-GW 431. The MAG in femtocell relay 410 may alsoexchange some of the UE data with the LMA in P-GW 434 over a PMIP GREtunnel through router 451, router 453, and Se-GW 438.

For Voice over LTE (VoLTE) or other Internet Multimedia Subsystem (IMS)services, the MAG in femtocell relay 410 and the LMA in a VoLTE P-GW(not shown) establish VoLTE PMIP GRE tunnels upon femtocell relayattachment. The VoLTE PMIP GRE tunnels traverse both the LAN/WAN andLWA/LTE interfaces. The VoLTE PMIP GRE tunnels each transport F-S2a andF-S5 user data flows that carry user audio/video data and SessionInitiation Protocol (SIP) signaling.

Femtocell relay 410 terminates the UE signaling and transfers Non-AccessStratum (NAS) messages between UE 403 and MME 432 in its own LTEFemtocell (F) signaling. Femtocell relay 410 may exchange itsF-signaling with R-GW 437 in an LTE signaling tunnel through picocellrelay 420, eNodeB 421, S-GW 431, and P-GW 434. Femtocell relay 410 mayalso exchange its F-signaling with R-GW 437 in another LTE signalingtunnel through router 451, router 453, and Se-GW 438. R-GW 437 exchangesthe F-signaling with eNodeB 421 (F-X2), MME 432 (F-S1-MME and F-S11),P-GW 434 (F-PMIP), other P-GWs (F-PMIP), PCRF 435 (F-S15), and ACCT 436(F-Gz/Gy).

Femtocell relay 410 has associated LTE Access Point Names (APNs) toestablish its user data and signaling bearers. A femto data APN supportsthe F-S5/2a user data flows in the PMIP GRE tunnel between the MAG infemtocell relay 410 and the LMA in P-GW 434 through picocell relay 420,eNodeB 421, and S-GW 431. For IMS services like VoLTE, the femto dataAPN also supports F-S5/2a user data flows in a VoLTE PMIP GRE tunnelbetween the MAG in femtocell relay 410 and the LMA in a VoLTE P-GW (notshown) through picocell relay 420, eNodeB 421, and S-GW 431. A femtosignaling APN supports the LTE signaling tunnel (F-X2, F-S1-MME, F-S11,F-S15, F-PMIP, and F-Gz/Gy) between femtocell relay 410 and R-GW 437through picocell relay 420, eNodeB 421, S-GW 431, and P-GW 434. R-GW 437supports the femto signaling APN by exchanging the LTE signaling witheNodeB 421 (F-X2), MME 432 (F-S1-MME, F-S11), P-GW 434 (F-PMIP), otherP-GWs (F-PMIP), PCRF 435 (F-S15), and ACCT 436 (F-Gz/Gy).

Referring to FIG. 6, a Local Mobility Anchor (LMA) in P-GW 434 iscoupled to a Mobile Access Gateway (MAG) in the L-SGW of picocell relay420. UE 402 has a UE data bearer and a UE signaling bearer with picocellrelay 420. The L-SGW in picocell relay 420 may exchange some of the userdata with the Internet over routers 452-453 in a LIPA data service. TheMAG in picocell relay 420 may exchange some of the user data with theLMA in P-GW 434 over a PMIP GRE tunnel through eNodeB 421 and S-GW 431.The MAG in picocell relay 420 may also exchange some of the user datawith the LMA in P-GW 434 over a PMIP GRE tunnel through routers 452-453and Se-GW 438.

For VoLTE or other IMS services, the MAG in picocell relay 420 and theLMA in a VoLTE P-GW (not shown) establish VoLTE PMIP GRE tunnels uponpicocell relay attachment. The VoLTE PMIP GRE tunnels traverse both theLAN/WAN and LWA/LTE interfaces. The VoLTE PMIP GRE tunnels transportP-S2a and P-S5 user data flows that carry user voice data and SessionInitiation Protocol (SIP) signaling.

Picocell relay 420 terminates the UE signaling and transfers Non-AccessStratum (NAS) messages between UE 402 and MME 432 in its own LTEPicocell (P) signaling. Picocell relay 420 may exchange its P-signalingwith R-GW 437 over eNodeB 421, S-GW 431, and P-GW 434. Picocell relay420 may also exchange its P-signaling with R-GW 437 over routers 452-453and Se-GW 438. R-GW 437 exchanges the P-signaling with eNodeB 421(P-X2), MME 432 (P-S1-MME and P-S11), P-GW 434 and others (PMIP), PCRF435 (P-S15), and ACCT 436 (F-Gz/Gy).

Picocell relay 420 has associated LTE APNs to establish its user dataand signaling bearers. A pico data APN supports the F-S5/2a user data inthe PMIP GRE tunnel between the MAG in picocell relay 420 and the LMA inP-GW 434 through eNodeB 421 and S-GW 431. For IMS services like VoLTE,the pico data APN also supports F-S5/2a user data flows in a VoLTE PMIPGRE tunnel between the MAG in picocell relay 420 and the LMA in a VoLTEP-GW (not shown) through eNodeB 421 and S-GW 431. A pico signaling APNsupports the LTE signaling tunnel (P-X2, P-S1-MME, P-S11, P-S15, P-PMIP,and P-Gz/Gy) between picocell relay 420 and R-GW 437 through eNodeB 421,S-GW 431, and P-GW 434. R-GW 437 supports the pico signaling APN byexchanging the picocell LTE signaling with eNodeB 421 (P-X2), MME 432(P-S1-MME, P-S11), P-GW 434 and others (PMIP), PCRF 435 (P-S15), andACCT 436 (F-Gz/Gy).

FIG. 7 illustrates femtocell relay 410. Femtocell relay 410 comprisesLWA eNodeB 423, L-SGW/MAG 701, Local Charging Data Function and ChargingTrigger Function (L-CDF/CTF) 702, Local Policy and Charging RulesFunction (L-PCRF) 703, Ethernet system 704, and LWA UE 404. LWA eNodeB423 exposes LTE and WiFi interfaces to UEs and broadcasts WiFi SSIDs andLTE PLMN IDs for FEMTO UE DATA and FEMTO UE VOLTE.

LWA eNodeB 423 applies RoHC compression/decompression to the user dataexchanged with UEs over the LTE and WiFi links. LWA eNodeB 423 appliesgeneral compression/decompression to the LTE signaling exchanged withthe UEs over the WiFi and LTE links. LWA UE 404 also applies RoHCcompression/decompression to the F-S5/2a user data exchanged over theLWA/LTE links. UE 404 applies general compression/decompression to theLTE signaling exchanged over the LWA/LTE links. UE 404 and eNodeB 423apply LTE QCIs as directed.

For user data, eNodeB 423 exchanges the user data over the F-S1U withL-SGW/MAG 701. L-SGW/MAG 701 terminates the F-S1U user data from eNodeB423. L-SGW/MAG 701 forms an endpoint for the PMIP GRE tunnels to P-GW434 over the LAN/WAN and LWA/LTE interfaces. L-SGW/MAG 701 performsbridging, formatting, and filtering on the user data from the F-S1U toform F-S2a and F-S5 user data.

L-SGW/MAG 701 and Ethernet system 704 exchange some user data F-S2a(1)and F-S5(1) over the PMIP GRE tunnels that traverse the LAN/WAN.L-SGW/MAG 701 and Ethernet system 704 exchange other user data F-S2a(2)and F-S5(2) over the other PMIP GRE tunnels that traverse LWA/LTE.L-SGW/MAG 701 and Ethernet system 704 may also exchange user data withthe Internet over the LAN/WAN for a LIPA service.

For femtocell signaling, eNodeB 423 and Ethernet system 704 exchangesome LTE signaling (F-S1-MME(1) and F-X2(1)) for LAN/WAN backhaul andexchange other signaling (F-S1-MME(2) and F-X2(2)) for LWA/LTE backhaul.L-SGW/MAG 701 and Ethernet system 704 exchange some LTE signaling(F-S11(1) and F-PMIP (1)) for LAN/WAN backhaul and exchange othersignaling (F-S11(2) and F-PMIP (2)) for LWA/LTE backhaul. Likewise,L-CDF/CTF 703 and Ethernet system 704 exchange some LTE signaling(F-Gz/Gy(1)) for LAN/WAN backhaul and exchange other signaling(F-Gz/Gy(2)) for LWA/LTE backhaul. L-PCRF 703 and Ethernet system 704exchange some LTE signaling (F-S15(1)) for LAN/WAN backhaul and exchangeother signaling (F-S15 (2)) for LWA/LTE backhaul.

Advantageously, L-SGW 701 has multiple backhaul options for its LTEsignaling and user data through Ethernet system 704. Ethernet system 704obtains LTE network access over the LAN/WAN. LWA UE 404 obtains LTEnetwork access over LWA/LTE for Ethernet system 704. Ethernet system 704aggregates and routes femtocell signaling and user data over theseinterfaces. Like eNodeB 423, L-SGW/MAG 701, and UE 404, Ethernet system704 applies LTE Quality-of-Service (QoS) to its bearers as indicated bythe specified LTE QoS Class Identifiers (QCIs).

To translate between LTE and Ethernet QoS, Ethernet system 704 appliesDifferentiated Services (DS) to its bearers to match its QoS to thecorresponding LTE QCI metrics. Thus, Ethernet system 704 exchanges LTEsignaling using DS Point Codes (DSCPs) that correspond to QCI 5.Ethernet system 704 exchanges F-S5/2a user data using DSCPs thatcorrespond to QCI 1, QCI 5, QCI 9, or some other QoS. For VoLTE, L-SGW701 maps between QCI 1 (voice) and QCI 5 (signaling) on the F-S1Uinterface and corresponding DSCPs for voice and signaling in theF-S5/S2a PMIP GRE tunnels. The other elements of femtocell relay 410(423, 702, 703, 404) may also use DSCP in a similar manner for theirtraffic and QCIs.

L-SGW/MAG 701 has a Children's Internet Protection Act (CIPA) filterapplication to filter user data. Macrocell PCRF 435 has a CIPA pitcherthat transfers CIPA filter flags and configuration data to L-PCRF 703over the F-S15 links. L-PCRF 703 transfers the CIPA filter flags andconfiguration data to the CIPA application in L-SGW 701. L-SGW 701filters the F-S1U user data using in the CIPA filter application asconfigured by macro PCRF 435.

FIG. 8 illustrates picocell relay 420. Picocell relay 420 comprises LWAeNodeB 422, L-SGW/MAG 801, L-CDF/CTF 802, L-PCRF 803, Ethernet system804, and LTE UE 405. LWA eNodeB 422 exposes LTE and WiFi interfaces toUEs and broadcasts WiFi SSIDs and LTE PLMN IDs for PICO RELAY, PICO UEDATA, and PICO UE VOLTE.

LWA eNodeB 422 applies RoHC compression/decompression to the user dataexchanged over the LTE and WiFi links. LWA eNodeB 422 applies generalcompression/decompression to the LTE signaling exchanged over the LTEand WiFi links. UE 405 applies RoHC compression/decompression to theuser data exchanged over the LTE links. UE 405 applies generalcompression/decompression to the LTE signaling exchanged over the LTElinks. UE 405 and eNodeB 422 apply LTE QCIs as directed.

For user data, eNodeB 422 exchanges the user data over the P-S1U withL-SGW/MAG 801. L-SGW/MAG 801 terminates the P-S1U user data from eNodeB422. L-SGW/MAG 801 forms an endpoint for the PMIP GRE tunnels to P-GW434. L-SGW/MAG 801 performs bridging, formatting, and filtering on theuser data from the P-S1U to form P-S2a and P-S5 user data. L-SGW/MAG 801and Ethernet system 804 exchange user data P-S2a(1) and P-S5(1) for thePMIP GRE tunnels that traverse the LAN/WAN. L-SGW/MAG 801 and Ethernetsystem 804 exchange user data P-S2a(2) and P-S5(2) for the PMIP GREtunnels that traverse LWA/LTE. L-SGW/MAG 801 and Ethernet system 804 mayalso exchange user data with the Internet over the LAN/WAN for a LIPAservice.

For picocell signaling, eNodeB 422 and Ethernet system 804 exchange someLTE signaling (P-S1-MME(1) and P-X2(1)) for LAN/WAN backhaul andexchange other signaling (P-S1-MME(2) and P-X2(2)) for LTE backhaul.L-SGW/MAG 801 and Ethernet system 804 exchange some LTE signaling(P-S11(1) and P-PMIP (1)) for LAN/WAN backhaul and exchange othersignaling (P-S11(2) and P-PMIP (2)) for LTE backhaul. Likewise,L-CDF/CTF 803 and Ethernet system 804 exchange some LTE signaling(P-Gz/Gy(1)) for LAN/WAN backhaul and exchange other signaling(P-Gz/Gy(2)) for LTE backhaul. L-PCRF 804 and Ethernet system 804exchange some LTE signaling (P-S15(1)) for LAN/WAN backhaul and exchangeother signaling (P-S15 (2)) for LTE backhaul.

Advantageously, L-SGW 801 has multiple backhaul options for itssignaling and user data through Ethernet system 804. Ethernet system 804obtains network access over the LAN/WAN. LTE UE 405 obtains networkaccess over LTE for Ethernet system 804. Ethernet system 804 aggregatesand routes picocell signaling and user data Like eNodeB 422, L-SGW 801,and UE 405, Ethernet system 804 applies LTE QoS to its bearers asindicated by the specified LTE QCIs.

To translate between LTE and Ethernet QoS, Ethernet system 804 appliesDiff Sery (DS) to its bearers to match its QoS to the corresponding LTEQCI metrics. Thus, Ethernet system 804 exchanges LTE signaling using DSPoint Codes (DSCPs) that correspond to QCI 5. Ethernet system 804exchanges F-S2a user data using DSCPs that correspond to QCI 1, QCI 5,QCI 9, or some other QoS. For VoLTE, L-SGW 801 maps between QCI 1(voice) and QCI 5 (signaling) on the P-S1U interface and correspondingDSCPs for voice and signaling in the P-S5/S2a PMIP GRE tunnels. Theother elements of picocell relay 420 (422, 802, 803, 405) may also useDSCP in a similar manner for their traffic and QCIs.

For the femtocell signaling and user data, LWA eNodeB 422 applies RoHCcompression/decompression to the user data (F-S2a(2) and F-S5(2)) thattraverses the femtocell's PMIP GRE tunnels. LWA eNodeB 422 appliesgeneral compression/decompression to the femtocell LTE signaling(F-S1-MME(2), F-X2(2), F-S11(2), F-S15(2), F-PMIP (2), and F-Gz/Gy(2))that traverses the signaling tunnel. L-SGW/MAG 801 terminates the P-S1Uhaving picocell user data, femtocell user data, and femtocell signaling.L-SGW 801, Ethernet system 804, and LTE UE 405 exchange the femtocelldata over the F-S5 and F-S2a PMIP GRE tunnels using the requisiteQCI/DSCP QoS. L-SGW 801, Ethernet system 804, and LTE UE 405 exchangethe femtocell signaling over the femto signaling tunnel using therequisite QCI/DSCP QoS.

L-SGW/MAG 801 has a Children's Internet Protection Act (CIPA) filterapplication to filter user data. Macrocell PCRF 435 has a CIPA pitcherthat transfers CIPA filter flags and configuration data to L-PCRF 803over the P-S15 links. L-PCRF 803 transfers the CIPA filter flags andconfiguration data to the CIPA application in L-SGW 801. L-SGW 801filters the P-S1U using in the CIPA filter application as configured bymacro PCRF 435.

FIG. 9 illustrates macrocell eNodeB 421 and S-GW 431. Macrocell eNodeB421 comprises LTE transceiver 901 and S1 interface 903. S-GW 431comprises S1 interface 904, S5 interface 905, and S11 interface 906. LTEtransceiver 901 exposes LTE interfaces to UEs, femtocell relays, andpicocell relays. LTE transceiver 901 broadcasts LTE PLMN IDs for MACROUE DATA, MACRO UE VOLTE, and MACRO RELAY.

For the typical UE, LTE transceiver 901 exchanges its LTE signaling anduser data (M-S1-MME and M-S1U) with S1 interface 903. For femtocell andpicocell relays, LTE transceiver 901 applies RoHCcompression/decompression to the user data that traverses F-S5(2),F-S2a(2), P-S5(2), and P-S2a(2) PMIP GRE tunnels. LTE transceiver 901applies general compression/decompression to the femtocell and picocellsignaling (F-S1-MME(2), F-S11(2), F-PMIP (2), F-X2(2), F-Gz/Gy(2),F-S15(2), P-S1-MME(2), P-S11(2), P-PMIP (2), P-X2(2), P-Gz/Gy(2), andP-S15(2)) exchanged over the LTE signaling tunnels. LTE transceiver 901and S1 interface 903 exchange the femtocell and picocell signaling anduser data.

S1 interface 903 exchanges macro signaling (M-S1-MME) with MME 432. S1interface 903 exchanges user data (M-S1U) with S1 interface 904 of S-GW431. The M-S1U interface transports the femtocell and picocell signalingand user data (F-S1-MME(2), F-S11(2), F-PMIP (2), F-X2(2), F-Gz/Gy(2),F-S15(2), P-S1-MME(2), P-S11(2), P-PMIP (2), P-X2(2), P-Gz/Gy(2),P-S15(2), F-S5(2), F-S2a(2), P-S5(2), and P-S2a(2)). S1 interface 904exchanges the femtocell and picocell signaling and user data with S5interface 905. S5 interface 905 exchanges user data (M-S5) with P-GW434. The M-S5 interface transports the femtocell and picocell signalingand user data. S11 interface 906 exchanges macro signaling (M-S11) withMME 432.

Macro eNodeB 421 and S-GW 431 apply LTE QoS to the bearers as indicatedby the specified QCIs. Macro eNodeB 421 and S-GW 431 exchange the LTEsignaling using QCI 5. Macro eNodeB 421 and S-GW 431 exchange theF-S5/2a and P-S5/2a user data using QCI 1, QCI 5, QCI 9, or some otherdata QoS.

FIG. 10 illustrates macrocell P-GW 434 and R-GW 437. Macro S-GW 431 andSe-GW 438 are shown again for reference. Macrocell P-GW 434 comprises S5interface 1001, Local Mobility Anchor (LMA) 1002, and SGi interface1003. R-GW 437 comprises SGi interface 1004, S1-MME interface 1005, S11interface 1006, X2 interface 1007, S15 interface 1008, G interface 1009,and PMIP interface 1010. Macrocell P-GW 434 exchanges its M-Gx data withPCRF 435 and exchanges its M-Gz/Gy data with ACCT 436.

In P-GW 434, S5 interface 1001 exchanges the user data (F-S2a(1)(2),F-S5(1)(2), P-S2a(1)(2), and P-S5(1)(2)) with LMA 1002 for PMIP GREtunnel termination. LMA 1002 exchanges the user data with SGi interface1003. SGi interface 1003 performs functions like routing and filteringon the user data for exchange with the Internet, IMS, or some othersystem over the SGi links.

In P-GW 434, S5 interface 1001 exchanges LTE signaling (F-S1-MME(2),F-S11(2), F-PMIP (2), F-X2(2), F-Gz/Gy(2), F-S15(2), P-S1-MME(2),P-S11(2), P-PMIP (2), P-X2(2), P-Gz/Gy(2), and P-S15(2)) with SGiinterface 1003. SGi interface 1003 exchanges the LTE signaling with SGiinterface 1004 in R-GW 437. In R-GW 437, SGi interface 1004 alsoreceives LTE signaling (F-S1-MME(1), F-S11(1), F-X2(1), F-Gz/Gy(1),F-S15(1), F-PMIP (1), P-S1-MME(1), P-S11(2), P-X2(1), P-Gz/Gy(1),P-S15(1), and P-PMIP (1)) from Se-GW 438. SGi interface 1004 performsfunctions like routing and filtering on the LTE signaling.

SGi interface 1004 exchanges the LTE signaling with proxy interfaces1005-1010, and proxy interfaces 1005-1010 exchange the LTE signalingwith various systems. Proxy interfaces 1005-1010 aggregate the LTEsignaling that was exchanged over the LAN/WAN backhaul and over theLWA/LTE backhaul. S1-MME interface 1005 exchanges the F-S1-MME andP-S1-MME signaling with MME 432. S11 interface 1006 exchanges F-S11 andP-S11 signaling with MME 432. X2 interface 1007 exchanges F-X2 and P-X2signaling with macrocell eNodeB 421. S15 interface 1008 exchanges F-S15and P-S15 signaling with PCRF 435. G interface 1009 exchanges F-Gz/Gyand P-Gz/Gy signaling with ACCT 436. PMIP interface 1010 exchangesF-PMIP and P-PMIP signaling with P-GW 434 and other P-GWs.

Macro P-GW 434 applies LTE QoS to the bearers as indicated by thespecified QCIs. Macro P-GW 434 exchanges the LTE signaling using QCI 5.P-GW 434 exchanges the user data using a QCI 1, QCI 5, QCI 9, or someother data QoS. R-GW 437 applies a QCI 5 type QoS to its signaling data.

The VoLTE P-GWs are configured in a similar manner to P-GW 434. TheVoLTE P-GWs comprise S5 interfaces, LMAs, and SGi interfaces. The VoLTEP-GWs terminate the PMIP GRE tunnels to the femtocell and pico cellrelays for user voice data and SIP/IMS signaling. The VoLTE P-GWsperform functions like routing and filtering on the user voice data andsignaling for exchange over their SGi links. Typically, the VoLTE P-GWsdo not backhaul femtocell and picocell LTE signaling. The VoLTE P-GWsapply LTE QoS to the bearers as indicated by the specified QCIs/DSCPs.The VoLTE P-GWs exchanges the IMS/SIP signaling using QCI 5. The VoLTEP-GWs exchanges the user voice data using a QCI 1.

FIG. 11 illustrates picocell relay 420 attachment to macrocell eNodeB421 to establish the picocell LTE data bearers and the picocell LTEsignaling bearer. Picocell relay 420 may also attach to the LAN/WAN andSe-GW 437. These LAN/WAN/LTE attachments could be standard and are notshown for clarity. Picocell relay 420 responds to the PLMN ID ofMACRO-RELAY from eNodeB 421 during an LTE attachment session. Picocellrelay 420 transfers information for MME 432 to eNodeB 421 in aNon-Access Stratum (NAS) message during the attachment. In response tothe LTE attachment, eNodeB 423 transfers a Macro (M) S1-MME initial UEmessage containing the NAS message to MME 432. MME 432 authorizespicocell relay 420 and retrieves the picocell DATA APN and the picocellsignaling (SIG) APN from HSS 433.

MME 432 selects P-GW 434 and a VoLTE P-GW based on the picocell DATA APNand transfers an M-S11 create session request (RQ) having the picocellAPNs to S-GW 431. Responsive to the M-S11 create session request, S-GW431 transfers a corresponding M-S5 create session request having thepicocell APNs to P-GW 434. P-GW 434 transfers a Macro (M) Credit ControlRequest (CCR) with the picocell ID and APNs DATA and SIG to PCRF 435.PCRF returns a Macro Credit Control Answer (M-CCA) that indicates QCI 9for the DATA APN and QCI 5 for the SIG APN. P-GW 434 selects IPaddresses for picocell relay 420 and transfers the pico IP addresses,APNs, and QCIs to S-GW 431 in an M-S5 create session response (RP). S-GW431 transfers the pico IP addresses, APNs, and QCIs for picocell relay420 to MME 432 in an M-S11 create session response.

In response to the M-S11 create bearer request for QCIs 9 and 5, MME 432transfers an M-S1-MME message to eNodeB 421. The M-S1-MME message has aninitial context set-up request and Attach (ATT) acceptance that indicatethe pico IP addresses, APNs, and QCIs for picocell relay 420. Inresponse to the S1-MME message, eNodeB 421 and picocell 420 perform anLTE attach acceptance session that delivers the pico IP addresses, APNs,and QCIs to picocell relay 420. In response to the LTE attachacceptance, eNodeB 421 transfers an S1-MME initial context response andattach complete (OK) message to MME 432. In response, MME 432 transfersan M-S11 modify bearer request to S-GW 431 which returns an M-S11 modifybearer response to MME 432.

Picocell relay 420 may now exchange picocell user data with P-GW 434over the PMIP GRE tunnel that traverses the LTE/M-S1U/M-S5 interfaces ofeNodeB 421 and S-GW 431. P-GW 434 exchanges the user data with externalsystems. Picocell relay 420 may now exchange picocell signaling withR-GW 437 over the signaling bearer that traverses theLTE/M-S1U/M-S5/M-SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434.R-GW 437 exchanges this picocell signaling with eNodeB 421, MME 432,P-GW 434, PCRF 435, and ACCT 436.

Although not shown for clarity, picocell relay 420 uses its P-S1-MMEinterface to initiate a VoLTE service request to MME 432 after its LTEattachment is complete. MME 432 and picocell relay 420 then interact toestablish VoLTE PMIP GRE tunnels between picocell L-SGW/MAG 801 and theVoLTE P-GW/LMA over the LTE/S1U/S5 interface. Typically, picocellL-SGW/MAG 801 and the VoLTE P-GW/LMA establish another VoLTE PMIP GREtunnel over the LAN/WAN. FIG. 14 shows this service request procedurefor femtocell relay 410.

FIG. 12 illustrates UE 402 attachment to picocell 420 to use the PMIPGRE data tunnel. UE 402 responds to the SSIDs or PLMN IDs of PICO UEDATA and PICO UE VoLTE from picocell relay 420 (eNodeB 422) during anLWA attachment session. UE 402 transfers information for MME 432 in aNAS message during LWA attachment. In response to the UE attachment,picocell relay 420 selects R-GW 437 and transfers a Picocell (P) S1-MMEinitial UE message containing the NAS message to R-GW 437. The P-S1-MMEmessage uses the picocell signaling bearer that traverses theLTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434. TheP-S1-MME initial UE message indicates the IP address for picocell relay420. R-GW 437 transfers the P-S1-MME initial UE message to MME 432.

MME 432 authorizes UE 402 and retrieves UE APNs DATA and VOLTE from HSS433 based on the UE ID and the SSID/PLMN IDs. In some examples,additional UE APNs are implemented like VIDEO. MME 432 responds to R-GW437 with the UE APNs in a P-S11 create session request. R-GW 437transfers the P-S11 create session request with the UE 402 APNs topicocell relay 420 (L-SGW 801) over the picocell signaling bearer thattraverses the SGi/S5/S1U/LTE interfaces of P-GW 434, S-GW 431, andeNodeB 421.

In response to the P-S11 create session message, picocell relay 420 (MAG801) transfers a P-PMIP proxy binding update message to P-GW 434 (LMA1002) over the picocell signaling bearer that traverses theLTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, P-GW 434, and R-GW437. The P-PMIP proxy binding update indicates the IP address ofpicocell relay 420. In response to the P-PMIP proxy binding update, P-GW434 (LMA 1002) selects IP addresses for UE 402 and binds UE 402 to thepicocell 420 IP address. P-GW 434 sends an M-CCR with the UE ID and APNsto PCRF 435. PCRF 435 returns a CCA for UE 402 that indicates QCI 9 theDATA APN and QCIs 5 and 1 for the VOLTE APN.

P-GW 434 (LMA 1002) returns a P-PMIP proxy binding acknowledgement (ACK)to picocell relay 420 over the picocell signaling bearer that traversesthe SGi/S5/S1U/LTE interfaces of R-GW 437, P-GW 434, S-GW 431, andeNodeB 421. The PMIP acknowledgement indicates the UE 402 IP addresses,APNs, and QCIs. In response to the P-PMIP acknowledgement, picocellrelay 420 (L-SGW 801) transfers a P-S11 create session response to R-GW437 over the picocell signaling bearer that traverses the LTE/S1U/S5/SGiinterfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers theP-S11 create session response to MME 432.

In response to the P-S11 create session response for the UE QCIs, MME432 returns a P-S1-MME message to R-GW 437. The P-S1-MME message has aninitial context request and attach acceptance and indicates the IPaddresses, APNs, and QCIs for UE 402. R-GW 437 transfers the P-S1-MMEmessage to picocell relay 420 over the picocell signaling bearer thattraverses the SGi/S5/S1U/LTE interfaces of P-GW 434, S-GW 431, andeNodeB 421.

In response to the P-S1-MME message, UE 402 and picocell 420 (eNodeB422) perform an LWA attach acceptance session over LTE or WiFi thatdelivers the UE IP addresses, APN DATA/QCI 9, and APN VOLTE/QCI 5 & 1 toUE 402. In response to the LTE attach acceptance, picocell relay 420(eNodeB 422) transfers a P-S1-MME initial context response and attachcomplete message to R-GW 437 over the picocell signaling bearer thattraverses the LTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, andP-GW 434. R-GW 437 transfers the P-S1-MME initial context response andattach complete to MME 432.

In response to the P-S1-MME initial context response and attachcomplete, MME 432 transfers a P-S11 modify bearer request to R-GW 437.R-GW 437 transfers the P-S11 modify bearer request to picocell relay 420over the picocell signaling bearer that traverses the SGi/S5/S1U/LTEinterfaces of P-GW 434, S-GW 431, and eNodeB 421. In response to theP-S11 modify bearer request, picocell relay 420 (L-SGW 801) transfers amodify bearer response to R-GW 437 over the picocell signaling bearerthat traverses the LTE/S1U/S5 interfaces of eNodeB 421, S-GW 431, andP-GW 434. R-GW 437 transfers the P-S11 modify bearer response to MME432.

Although not shown for clarity, UE 402 may exchange user data withpicocell relay 420 over LWA based on QCIs 1, 5, and 9. Picocell relay420 may exchange the user data with P-GW 434 over the PMIP GRE tunnelthat traverses the LTE/S1U/S5 interfaces of eNodeB 421 and S-GW 431based on QCI 9. Picocell relay 420 may exchange IMS signaling with theVoLTE P-GW (and IMS) over the VoLTE PMIP GRE tunnel that traverses theLTE/S1U/S5 interfaces of eNodeB 421 and S-GW 431 based on QCI 5.Picocell relay 420 may exchange voice data with the VoLTE P-GW over theVoLTE PMIP GRE tunnel that traverses the LTE/S1U/S5 interfaces of eNodeB421 and S-GW 431 based on QCI 1.

FIG. 13 illustrates femtocell relay 410 attachment to picocell relay 420to establish the femtocell user data bearer and the femtocell signalingbearer. Femtocell relay 420 also attaches to the LAN/WAN and Se-GW 437.These LAN/WAN/LTE attachments could be standard and are not shown forclarity. Femtocell relay 410 responds to the SSID or PLMN ID ofPICO-RELAY from picocell 420 (eNodeB 422) during an LWA attachmentsession using LTE or WiFi. Femtocell 410 transfers information for MME432 in a NAS message during LWA attachment. In response to the femtocellattachment, picocell relay 420 transfers a P-S1-MME initial UE messagecontaining the NAS message to R-GW 437. The P-S1-MME message uses thefemtocell signaling bearer traverses the LTE/S1U/S5/SGi interfaces ofeNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers the P-S1-MMEinitial UE message to MME 432.

MME 432 authorizes femtocell relay 410 and retrieves the femtocell APNsDATA and SIG from HSS 433. MME 432 selects P-GW 434 and a VoLTE P-GWbased on the femtocell DATA APN. MME 432 responds to R-GW 437 with thefemtocell APNs in a P-S11 create session request. R-GW 437 transfers theP-S11 create session request with the femtocell APNs to picocell relay420 (L-SGW 801) over the picocell signaling bearer that traverses theSGi/S5/S1U/LTE interfaces of P-GW 434, S-GW 431, and eNodeB 421. Inresponse to the P-S11 create session request, picocell relay 420 (MAG801) transfers a P-PMIP proxy binding update message to P-GW 434 (LMA1002) over the picocell signaling bearer that traverses theLTE/S1U/S5/SGi interfaces through eNodeB 421, S-GW 431, P-GW 434, andR-GW 437. The P-PMIP proxy binding update indicates the IP address forpicocell relay 420.

In response to the P-PMIP proxy binding update, P-GW 434 (LMA 1002)selects IP addresses for femtocell relay 410 and binds femtocell relay410 to the IP address for picocell relay 420. P-GW 434 sends an M-CCR toPCRF 435 for the femtocell DATA and SIG APNs. PCRF 435 returns an M-CCAfor femtocell relay 410 that typically indicates QCI 9 for the femtocelldata APN and QCI 5 for the femtocell signaling APN.

P-GW 434 (LMA 1002) returns a P-PMIP proxy binding acknowledgement topicocell relay 420 over the picocell signaling bearer that traverses theSGi/S5/S1U/LTE interfaces of R-GW 437, P-GW 434, S-GW 431, and eNodeB421. The PMIP acknowledgement indicates the femtocell relay IPaddresses, APNs, and QCIs. In response to the P-PMIP acknowledgement,picocell relay 420 (L-SGW 801) transfers a P-S11 create session responseto R-GW 437 over the picocell signaling bearer that traverses theLTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW437 transfers the P-S11 create session response to MME 432.

In response to the P-S11 create bearer request for QCIs 5 and 9, MME 432returns a P-S1-MME message to R-GW 437. The P-S1-MME message has aninitial context request and attach acceptance that indicate the IPaddresses, APNs, and QCIs for femtocell relay 410. R-GW 437 transfersthe P-S1-MME message to picocell relay 420 over the picocell signalingbearer that traverses the SGi/S5/S1U/LTE interfaces of P-GW 434, S-GW431, and eNodeB 421.

In response to the P-S1-MME message, femtocell relay 410 (UE 404) andpicocell relay 420 (eNodeB 422) perform an LWA attach acceptance sessionover LTE or WiFi that delivers the IP addresses, APNs, and QCIs forfemtocell relay 410 to femtocell relay 410. In response to the LWAattach acceptance, picocell relay 420 (eNodeB 422) transfers a P-S1-MMEinitial context response and attach complete (OK) message to R-GW 437over the picocell signaling bearer that traverses the LTE/S1U/S5/SGiinterfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers theP-S1-MME initial context response and attach complete to MME 432.

In response to the P-S1-MME initial context response and attachcomplete, MME 432 transfers a P-S11 modify bearer request to R-GW 437.R-GW 437 transfers the P-S11 modify bearer request to picocell relay 420over the picocell signaling bearer that traverses the SGi/S5/S1U/LTEinterfaces of P-GW 434, S-GW 431, and eNodeB 421. In response to theP-S11 modify bearer request, picocell relay 420 (L-SGW 801) transfers amodify bearer response to R-GW 437 over the picocell signaling bearerthat traverses the LTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431,and P-GW 434. R-GW 437 transfers the P-S11 modify bearer response to MME432.

Although not shown for clarity, femtocell relay 410 may exchange userdata with P-GW 434 over the PMIP GRE data bearer that traverses theLWA/LTE/S1U/S5 interfaces of picocell relay 420, eNodeB 421, and S-GW431. Femtocell relay 410 may also exchange femtocell signaling with R-GW437 over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. As shown below, femtocell relay 420 will send aF-S1-MME service request to establish a VoLTE PMIP GRE bearer to theselected VoLTE P-GW after the modify bearer messaging is complete.

FIG. 14 illustrates VoLTE service provisioning for femtocell relay 420.After LTE attachment, femtocell relay 420 (eNodeB 423), transfers anF-S1-MME initial UE service request containing a NAS message with aVoLTE request to R-GW 437. The F-S1-MME initial UE service request usesthe femtocell signaling bearer that traverses the LWA/LTE/S1U/S5/SGiinterfaces of picocell relay 420, eNodeB 421, S-GW 431, and P-GW 434.R-GW 437 transfers the F-S1-MME initial UE service request for VoLTE toMME 432.

In response to the F-S1-MME initial UE service request for VoLTE, MME432 selects a VoLTE P-GW/LMA for femtocell relay 410 to provide VoLTEQoS to attaching UEs. In response to the VoLTE service request, MME 432also returns an F-S1-MME initial context request to R-GW 437. R-GW 437transfers the F-S1-MME initial context request to femtocell relay 410(eNodeB 423) over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420.

In response to the F-S1-MME initial context request, femtocell relay 410(eNodeB 423) returns an F-S1-MME initial context response to R-GW 437over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S1-MME initial contextresponse to MME 432. In response to the F-S1-MME initial contextresponse, MME 432 transfers an F-S11 modify bearer request indicatingthe VoLTE P-GW to R-GW 437. R-GW 437 transfers the F-S11 modify bearerrequest to femtocell relay 410 (L-SGW 701) over the femtocell signalingbearer that traverses the SGi/S5/S1U/LTE/LWA interfaces of P-GW 434,S-GW 431, eNodeB 421, and picocell relay 420.

In response to the F-S11 modify bearer request identifying the VoLTEP-GW, femtocell relay 410 (L-SGW 701) transfers an F-PMIP proxy bindingupdate over the femtocell signaling bearer to the identified VoLTEP-GW/LMA. The F-PMIP proxy binding update traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, P-GW 434, and R-GW 437. The F-PMIP proxy binding update indicatesthe IP address of femtocell relay 410 and APN DATA. In response to theF-PMIP update message, the VoLTE P-GW/LMA sends an M-CCR to PCRF 435with the femto APN DATA and obtains an M-CCA for femtocell relay 410.The M-CCA is for one or more QCI 5 signaling bearers and QCI 1 voicebearers over the VoLTE PMIP GRE tunnel between femtocell relay 410 andthe VoLTE P-GW/LMA.

The VoLTE P-GW/LMA returns an F-PMIP acknowledgement to femtocell relay410 over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of R-GW 437, P-GW 434, S-GW 431, eNodeB421, and picocell relay 420. In response to the F-PMIP acknowledgement,femtocell relay 410 (L-SGW 701) transfers an F-S11 modify bearerresponse to R-GW 437 over the femtocell signaling bearer that traversesthe LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421,S-GW 431, and P-GW 434. R-GW 437 transfers the F-S11 modify bearerresponse to MME 432.

After UE 403 performs LWA attachment (FIG. 15), UE 403 may then exchangeSession Initiation Protocol (SIP) signaling with femtocell relay 410over LWA using LTE or WiFi by using its VoLTE APN and QCI 5 signalingbearer. Femtocell relay 410 and the VoLTE P-GW exchange the SIPsignaling over the VoLTE PMIP GRE tunnel based on QCI 5. The VoLTEP-GW/LMA typically exchanges the SIP signaling with an IMS (not shown)over an M-SGi link. If an IMS session is established (FIG. 17), then UE403 may exchange voice data with femtocell relay 410 over LWA using LTEor WiFi by using its VoLTE APN and QCI 1 voice bearer. Femtocell relay410 and the VoLTE P-GW exchange the voice data signaling over the VoLTEPMIP GRE tunnel based on QCI 1. The VoLTE P-GW/LMA typically exchangesthe voice data with a data network over an M-SGi link.

FIG. 15 illustrates UE 403 attachment to femtocell 420 to use thefemtocell PMIP GRE data bearer. UE 403 responds to the SSIDs or PLMN IDsof FEMTO UE DATA and FEMTO UE VOLTE from femtocell relay 410 (eNodeB423) during an LWA attachment session. UE 403 transfers information forMME 432 in a NAS message during LWA attachment. In response to UE 403attachment, femtocell relay 410 transfers a Femto (F) S1-MME initial UEmessage containing the NAS message to R-GW 437. The F-S1-MME messageuses the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S1-MME initial UE message toMME 432.

MME 432 authorizes UE 403 and retrieves UE APNs for DATA and VOLTE fromHSS 433. MME 432 selects P-GW 434 for the DATA APN and a VoLTE P-GW forthe VoLTE APN. MME 432 responds to R-GW 437 with the UE APNs and P-GWIDs in an F-S11 create session request. R-GW 437 transfers the F-S11create session request with the UE APNs and P-GW IDs to femtocell relay410 (L-SGW 701) over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420.

In response to the P-S11 create session request, femtocell relay 410(MAG 701) transfers an F-PMIP proxy binding update message to P-GW 434(LMA 1002) over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, P-GW 434, and R-GW 437. The F-PMIP update indicates the IP addressfor femtocell relay 410 and the APN DATA for UE 403. In response to theF-PMIP proxy binding update message, P-GW 434 (LMA 1002) selects IPaddresses for UE 403 and binds UE 403 to the IP address for femtocellrelay 410. P-GW 434 sends an M-CCR to PCRF 435 having the UE 403 APNs.PCRF 435 returns an M-CCA for UE 403 that indicates QCI 9 for DATA andQCIs 5 and 1 for VOLTE.

P-GW 434 (LMA 1002) returns an F-PMIP acknowledgement to femtocell relay410 over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of R-GW 437, P-GW 434, S-GW 431, eNodeB,and pico-cell relay 420. The F-PMIP acknowledgement indicates the UE 403IP addresses and QCIs, and in response to the F-PMIP acknowledgement,femtocell relay 410 (L-SGW 701) transfers an F-S11 create sessionresponse for the UE QCIs to R-GW 437 over the femtocell signaling bearerthat traverses the LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420,eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers the F-S11 createsession response to MME 432.

In response to the F-S11 create session response with the UE QCIs, MME432 returns an F-S1-MME message to R-GW 437. The F-S1-MME message has aninitial context request and attach acceptance and indicates the IPaddresses, APNs, QCIs, and P-GWs for UE 403. R-GW 437 transfers theF-S1-MME message to femtocell relay 410 over the femtocell signalingbearer that traverses the SGi/S5/S1U/LTE/LWA interfaces of P-GW 434,S-GW 431, eNodeB 421, and picocell relay 420.

In response to the F-S1-MME message, UE 403 and femtocell relay 420(eNodeB 423) perform an LWA attach acceptance session over LTE or WiFithat delivers the UE IP addresses, P-GW IDs, APNs DATA and VOLTE, andQCIs 9, 5, and 1 to UE 403. In response to the LWA attach acceptance,femtocell relay 420 (eNodeB 423) transfers an F-S1-MME initial contextresponse and attach complete message to R-GW 437 over the femtocellsignaling bearer that traverses the LWA/LTE/S1U/S5/SGi interfaces ofpicocell relay 420, eNodeB 421, S-GW 431, and P-GW 434. R-GW 437transfers the F-S1-MME initial context response and attach complete toMME 432.

In response to the F-S1-MME initial context response and attachcomplete, MME 432 transfers an F-S11 modify bearer request to R-GW 437.R-GW 437 transfers the F-S11 modify bearer request to femtocell relay420 over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420. In response to the F-S11 modify bearer request,femtocell relay 420 (L-SGW 701) transfers a modify bearer response toR-GW 437 over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S11 modify bearer responseto MME 432.

Although not shown for clarity, UE 403 may then exchange user data withfemtocell relay 410 over LWA based on the DATA (QCI 9) and VoLTE APNs(QCI 5 and 1). Femtocell relay 410 may exchange user data with P-GW 434over the PMIP GRE user data tunnel that traverses the LWA/LTE/S1U/S5interfaces of picocell 420, eNodeB 421, and S-GW 431. Femtocell relay410 may also exchange femtocell signaling for UE 403 with R-GW 437 overthe signaling bearer that traverses the LWA/LTE/S1U/S5/SGi interfaces ofpicocell relay 420, eNodeB 421, S-GW 431, and P-GW 434.

FIG. 16 illustrates UE 403 Internet service from femtocell relay 420. UE403 transfers an LWA internet connection request to femtocell relay 410(eNodeB 423). In response to the LWA internet connection request,femtocell relay 410 transfers an F-S1-MME initial UE service requestcontaining a NAS message with the internet connection request to R-GW437. The F-S1-MME message uses the femtocell signaling bearer thattraverses the LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420,eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers the F-S1-MMEinitial UE service request to MME 432.

In response to the F-S1-MME initial UE service request for internet, MME432 returns an F-S1-MME initial context request to R-GW 437. R-GW 437transfers the F-S1-MME initial context request to femtocell relay 410(eNodeB 423) over the femtocell signaling bearer that traverses theSGi/S5/S1U/lte/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420. In response to the F-S1-MME initial context request,femtocell relay 410 (eNodeB 423) returns an F-S1-MME initial contextresponse to R-GW 437 over the femtocell signaling bearer that traversesthe LWA/LTE/S1U/S5/M-SGi interfaces of picocell relay 420, eNodeB 421,S-GW 431, and P-GW 434. R-GW 437 transfers the F-S1-MME initial contextresponse to MME 432.

In response to the F-S1-MME initial context response, MME 432 transfersan F-S11 modify bearer request to R-GW 437. R-GW 437 transfers the F-S11modify bearer request to femtocell relay 410 (L-SGW 701) over thefemtocell signaling bearer that traverses the SGi/S5/S1U/LTE/LWAinterfaces of P-GW 434, S-GW 431, eNodeB 421, and picocell relay 420. Inresponse to the F-S11 modify bearer request, femtocell relay 410 (L-SGW701) transfers an F-PMIP proxy binding update over the femtocellsignaling bearer that traverses the LWA/LTE/S1U/S5/SGi interfaces ofpicocell relay 420, eNodeB 421, S-GW 431, P-GW 434, and R-GW 437. TheF-PMIP proxy binding update indicates the IP address for femtocell relay410 and the UE APN DATA and the service request metrics. In response tothe F-PMIP proxy binding update message, P-GW 434 (LMA 1002) selects IPaddresses for UE 403 and binds UE 403 to the IP address for femtocellrelay 410. P-GW 434 also sends an M-CCR with the APN DATA and theservice request metrics for UE 403 to PCRF 435. PCRF returns an M-CCAfor UE 403 that typically indicates QCI 9 for UE data, although the QCImay be upgraded based on the service request metrics or some otherfactor.

P-GW 434 (LMA 1002) returns an F-PMIP acknowledgement to femtocell relay410 over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of R-GW 437, P-GW 434, S-GW 431, eNodeB421, and pico-cell relay 420. The F-PMIP acknowledgement indicates theUE 403 IP addresses and QCIs. In response to the F-PMIP acknowledgement,femtocell relay 410 (L-SGW 701) transfers an F-S11 modify bearerresponse to R-GW 437 over the femtocell signaling bearer that traversesthe LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S11 modify bearer responseto MME 432.

UE 403 may then exchange user data with femtocell relay 410 over LWAbased on the DATA APN and the specified QCI. Femtocell relay 110exchanges the user data over the PMIP GRE tunnel with P-GW/MAG 434 basedon QCI 9 or some other QCI as specified by PCRF 435.

FIG. 17 illustrates UE 403 VoLTE service from femtocell relay 420. AfterLTE attachment, IMS registration, and SIP messaging by UE 403 (notshown), macro PCRF 435 receives an add VoLTE bearer request from IMS. Inresponse to the VoLTE bearer request, macro PCRF 435 transfers aFemtocell Re-Authorization Request (F-RAR) for a VoLTE to R-GW 434. R-GW434 transfers the F-RAR to femtocell relay 410 (L-PCRF 703) over theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420.

In response to the F-RAR for VoLTE in femtocell relay 420, L-PCRF 703transfers a gateway control request to L-SGW 701. In femtocell relay420, L-SGW 701 responsively transfers an F-S11 create bearer request forVoLTE to MME 432. The F-S11 create bearer request traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S11 create bearer request toMME 432.

In response to the M-S11 create bearer request for VoLTE, MME 432transfers an F-S1-MME create bearer/session management request for VoLTEto R-GW 437 for eNodeB423. R-GW 437 transfers the F-S1-MME createbearer/session management request to femtocell relay 410 (eNodeB 423)over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420. In response to the F-S1-MME create bearer/sessionmanagement request for VoLTE, femtocell relay 410 (eNodeB 423) sends aVoLTE LWA reconfiguration request to UE 403 and UE 403 reconfiguresitself for a QCI 1 voice bearer on the LWA access link.

After VoLTE LWA reconfiguration, femtocell relay 410 (eNodeB 423)returns an F-S1-MME create bearer/session management response to R-GW437 over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S1-MME create bearer/sessionmanagement response to MME 432. In response to the F-S1-MME createbearer/session management response for VoLTE, MME 432 transfers an F-S11create bearer response for VoLTE to R-GW 437. R-GW 437 transfers theF-S11 create bearer response to femtocell relay 410 (L-SGW 701) over thefemtocell signaling bearer that traverses the SGi/S5/S1U/LTE/LWAinterfaces of P-GW 434, S-GW 431, eNodeB 421, and picocell relay 420.

In response to the F-S11 modify bearer request for VoLTE in femtocellrelay 410, L-SGW 701 transfers a gateway control response for VoLTE toL-PCRF 703. In femtocell relay 410, L-PCRF 703 responsively sends anF-RAA for VoLTE to PCRF 435 over the femtocell signaling bearer thattraverses the LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420,eNodeB 421, S-GW 431, P-GW 434, and R-GW 437.

UE 403 may now exchange user voice data with femtocell relay 410 overLWA using LTE or WiFi based on the VoLTE APN and QCI 1. Femtocell relay410 and the VoLTE P-GW exchange the user voice over the VoLTE PMIP GREtunnel based on QCI 1. In femtocell relay 410, L-SGW 701 maps the QCI 1voice data on the LWA access link into a DSCP flow in the PMIP GREtunnel that has a QCI 1-level QoS. The VoLTE P-GW/LMA exchanges the uservoice data with external systems over its SGi interface. Other IMSservices like video and audio data conferencing could be implemented ina similar manner.

FIGS. 18-28 illustrate a variant of LTE data communication system 400that uses SGi tunnels between L-PGWs in relays 410 and 420 and macroP-GW 434. Referring to FIG. 18, UE 403 has a UE data bearer and a UEsignaling bearer with femtocell relay 410. The L-SGW in femtocell relay410 may exchange some of the UE data with the Internet over routers 451and 453 in a LIPA data service. The L-SGW in femtocell relay 410 mayexchange some of the UE data with P-GW 434 over an SGi tunnel throughpicocell relay 420, eNodeB 421, and S-GW 431. The L-SGW in femtocellrelay 410 may also exchange some of the UE data with P-GW 434 over anSGi tunnel through router 451, router 453, and Se-GW 438.

Femtocell relay 410 terminates the UE signaling and transfers Non-AccessStratum (NAS) messages between UE 403 and MME 432 in its own LTEFemtocell (F) signaling. Femtocell relay 410 may exchange itsF-signaling with R-GW 437 in a signaling tunnel through picocell relay420, eNodeB 421, S-GW 431, and P-GW 434. Femtocell relay 410 may alsoexchange its F-signaling with R-GW 437 in a signaling tunnel throughrouter 451, router 453, and Se-GW 438. R-GW 437 exchanges the femtocellLTE signaling with eNodeB 421 (F-X2), MME 432 (F-S1-MME and F-S11), PCRF435 (F-S15), and ACCT 436 (F-Gz/Gy).

Femtocell relay 410 has associated LTE Access Point Names (APNs) toestablish its user data and signaling bearers. A femto APN DATA supportsthe F-SGi user data bearer between the femtocell relay 410 and P-GW 434through picocell relay 420, eNodeB 421, and S-GW 431. A femto APN SIGsupports the signaling tunnel (F-X2, F-S1-MME, F-S11, F-S15, andF-Gz/Gy) between femtocell relay 410 and R-GW 437 through picocell relay420, eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 supports the femto SIGAPN by exchanging LTE signaling with eNodeB 421 (F-X2), MME 432(F-S1-MME and F-S11), PCRF 435 (F-S15), and ACCT 436 (F-Gz/Gy).

Referring to FIG. 19, UE 402 has a UE data bearer and a UE signalingbearer with picocell relay 420. The L-SGW in picocell relay 420 mayexchange some of the UE data with the Internet over routers 452-453 in aLIPA data service. The L-SGW in picocell relay 420 may exchange some ofthe UE data with P-GW 434 over an SGi tunnel through eNodeB 421 and S-GW431. The L-SGW in picocell relay 420 may also exchange some of the UEdata with P-GW 434 over an SGi tunnel through routers 452-453 and Se-GW438.

Picocell relay 420 terminates the UE signaling and transfers NASmessages between UE 402 and MME 432 in its own LTE Picocell (P)signaling. Picocell relay 420 may exchange its P-signaling with R-GW 437in a signaling tunnel through eNodeB 421, S-GW 431, and P-GW 434.Picocell relay 420 may also exchange its P-signaling with R-GW 437 in asignaling tunnel through routers 452-453 and Se-GW 438. R-GW 437exchanges the picocell LTE signaling with eNodeB 421 (P-X2), MME 432(P-S1-MME and P-S11), PCRF 435 (P-S15), and ACCT 436 (F-Gz/Gy).

Picocell relay 420 has associated LTE APNs to establish its user dataand signaling bearers. A pico APN DATA supports the F-SGi user datatunnel between the L-SGW picocell relay 420 and P-GW 434 through eNodeB421 and S-GW 431. A pico APN SIG supports the signaling tunnel (P-X2,P-S1-MME, P-S11, P-S15, and P-Gz/Gy) between picocell relay 420 and R-GW437 through eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 supports thepico SIG APN by exchanging picocell LTE signaling with eNodeB 421(P-X2), MME 432 (P-S1-MME, P-S11), PCRF 435 (P-S15), and ACCT 436(F-Gz/Gy).

FIG. 20 illustrates femtocell relay 410. Femtocell relay 410 comprisesLWA eNodeB 423, L-SGW 2001, Local Packet Data Network Gateway (L-PGW)2002, Local Policy and Charging Rules Function (L-PCRF) 2003, Ethernetsystem 2004, and LWA UE 404. LWA eNodeB 423 exposes LTE and WiFiinterfaces to UEs and broadcasts WiFi SSIDs and LTE PLMN IDs for FEMTOUE DATA and FEMTO UE VOLTE. LWA eNodeB 423 applies RoHCcompression/decompression to the user data exchanged with UEs over theLTE and WiFi links. LWA eNodeB 423 applies generalcompression/decompression to the LTE signaling exchanged with the UEsover the WiFi and LTE links. LWA UE 404 applies RoHCcompression/decompression to the F-SGi user data exchanged over theLWA/LTE links. UE 404 applies general compression/decompression to theLTE signaling exchanged over the LWA/LTE links.

For user data, eNodeB 423 exchanges the user data over the F-S1U withL-SGW 2001. L-SGW 2001 terminates the F-S1U user data from eNodeB 423.L-SGW 2001 performs bridging, formatting, and filtering on the userdata. L-SGW 2001 and Ethernet system 2004 may exchange some of the userdata with the Internet over the LAN/WAN for the LIPA service. L-SGW 2001and L-PGW 2002 exchange the other user data. L-PGW 2002 forms anendpoint for SGi data tunnels to macro P-GW 434 and LTE signalingtunnels to R-GW 437. L-PGW 2002 and Ethernet system 2004 exchange someuser data over the F-SGi (1) tunnel that traverses the LAN/WAN. L-PGW2002 and Ethernet system 2004 exchange other user data over the F-SGi(2) tunnel that traverses LWA/LTE.

Advantageously, L-PGW 2002 has multiple backhaul options for itssignaling and user data through Ethernet system 2004. Ethernet system2004 obtains network access over the LAN/WAN. LWA UE 404 obtains networkaccess over LWA/LTE for Ethernet system 2004. Ethernet system 2004aggregates and routes femtocell signaling and user data Like eNodeB 423,L-SGW 2001, L-PGW 2002, and UE 404, Ethernet system 2004 applies LTEQuality-of-Service (QoS) to its bearers as indicated by the specifiedLTE QoS Class Identifiers (QCIs).

To translate between LTE and Ethernet QoS, Ethernet system 2004 appliesDifferentiated Services (DS) to its bearers to match its QoS to thecorresponding LTE QCI metrics. Thus, Ethernet system 2004 exchanges LTEsignaling using DS Point Codes (DSCPs) that correspond to QCI 5.Ethernet system 2004 exchanges F-SGi user data using DSCPs thatcorrespond to QCI 1, QCI 5, QCI 9, or some other QoS. For VoLTE, L-SGW2001 maps between QCI 1 (voice) and QCI 5 (signaling) on the F-S1Uinterface and corresponding DSCPs for voice and signaling in the F-SGitunnels. The other elements of femtocell relay 410 (423, 2002, 2003,2004) may also use DSCP in a similar manner for their traffic and QCIs.

For femtocell signaling, eNodeB 423 and Ethernet system 2004 exchangesome LTE signaling (F-S1-MME(1) and F-X2(1)) for LAN/WAN backhaul andexchange other signaling (F-S1-MME(2) and F-X2(2)) for LWA/LTE backhaul.L-SGW 2001 and Ethernet system 2004 exchange some LTE signaling(F-S11(1)) for LAN/WAN backhaul and exchange other signaling (F-S11(2))for LWA/LTE backhaul. Likewise, L-PGW 2003 and Ethernet system 704exchange some LTE signaling (F-Gz/Gy(1)) for LAN/WAN backhaul andexchange other signaling (F-Gz/Gy(2)) for LWA/LTE backhaul. L-PCRF 2003and Ethernet system 2004 exchange some LTE signaling (F-S15(1)) forLAN/WAN backhaul and exchange other signaling (F-S15 (2)) for LWA/LTEbackhaul.

L-SGW 2001 has a Children's Internet Protection Act (CIPA) filterapplication to filter user data. Macrocell PCRF 435 has a CIPA pitcherthat transfers CIPA filter flags and configuration data to L-PCRF 2003over the F-S15 links. L-PCRF 2003 transfers the CIPA filter flags andconfiguration data to the CIPA application in L-SGW 2001. L-SGW 2001filters the F-S1U user data using in the CIPA filter application asconfigured by macro PCRF 435.

FIG. 21 illustrates picocell relay 420. Picocell relay 420 comprises LWAeNodeB 422, L-SGW 2101, L-PGW 2102, L-PCRF 2103, Ethernet system 2104,and LTE UE 405. LWA eNodeB 422 exposes LTE and WiFi interfaces to UEsand broadcasts WiFi SSIDs and LTE PLMN IDs for PICO RELAY, PICO UE DATA,and PICO UE VOLTE. LWA eNodeB 422 applies RoHC compression/decompressionto the user data exchanged over the LTE and WiFi links. LWA eNodeB 422applies general compression/decompression to the LTE signaling exchangedover the LTE and WiFi links. LTE UE 405 applies RoHCcompression/decompression to the P-SGi user data exchanged over theLWA/LTE links. UE 405 applies general compression/decompression to theLTE signaling exchanged over the LWA/LTE links.

For user data, eNodeB 422 exchanges the user data over the P-S1U withL-SGW 2101. L-SGW 2101 terminates the F-S1U user data from eNodeB 422.L-SGW 2101 performs bridging, formatting, and filtering on the userdata. L-SGW 2101 and Ethernet system 2104 may exchange some of the userdata with the Internet over the LAN/WAN for the LIPA service. L-SGW 2101and L-PGW 2102 exchange the other user data. L-PGW 2102 forms anendpoint for SGi data tunnels to macro P-GW 434 and LTE signalingtunnels to R-GW 437. L-PGW 2102 and Ethernet system 2104 exchange someuser data over the P-SGi (1) tunnel that traverses the LAN/WAN. L-PGW2102 and Ethernet system 2104 exchange other user data over the P-SGi(2) tunnel that traverses LWA/LTE.

Advantageously, L-PGW 2102 has multiple backhaul options for itssignaling and user data through Ethernet system 2104. Ethernet system2104 obtains network access over the LAN/WAN. LTE UE 405 obtains networkaccess over LTE for Ethernet system 2104. Ethernet system 2104aggregates and routes femtocell signaling and user data Like eNodeB 422,L-SGW 2101, L-PGW 2102, and UE 405, Ethernet system 2104 applies LTE QoSto its bearers as indicated by the specified LTE QCIs.

To translate between LTE and Ethernet QoS, Ethernet system 2104 appliesDifferentiated Services (DS) to its bearers to match its QoS to thecorresponding LTE QCI metrics. Thus, Ethernet system 2104 exchanges LTEsignaling using DSCPs that correspond to QCI 5. Ethernet system 2104exchanges F-SGi user data using DSCPs that correspond to QCI 1, QCI 5,QCI 9, or some other QoS. For VoLTE, L-SGW 2101 maps between QCI 1(voice) and QCI 5 (signaling) on the F-S1U interface and correspondingDSCPs for voice and signaling in the F-5/S2a PMIP GRE tunnels. The otherelements of picocell relay 420 (423, 2102, 2103, 404) may also use DSCPin a similar manner for their traffic and QCIs.

For picocell signaling, eNodeB 422 and Ethernet system 2104 exchangesome LTE signaling (P-S1-MME(1) and P-X2(1)) for LAN/WAN backhaul andexchange other signaling (P-S1-MME(2) and P-X2(2)) for LWA/LTE backhaul.L-SGW 2101 and Ethernet system 2104 exchange some LTE signaling(P-S11(1)) for LAN/WAN backhaul and exchange other signaling (P-S11(2))for LWA/LTE backhaul. Likewise, L-PGW 2103 and Ethernet system 2104exchange some LTE signaling (P-Gz/Gy(1)) for LAN/WAN backhaul andexchange other signaling (P-Gz/Gy(2)) for LWA/LTE backhaul. L-PCRF 2103and Ethernet system 2104 exchange some LTE signaling (P-S15(1)) forLAN/WAN backhaul and exchange other signaling (P-S15 (2)) for LWA/LTEbackhaul.

For the femtocell signaling and user data, LWA eNodeB 422 applies RoHCcompression/decompression to the user data (F-SGi(2)) that traverses thefemtocell's SGi tunnels. LWA eNodeB 422 applies generalcompression/decompression to the femtocell LTE signaling (F-S1-MME(2),F-X2(2), F-S11(2), F-S15(2), and F-Gz/Gy(2)) that traverses thesignaling tunnel. L-SGW/MAG 2101 terminates the P-S1U having picocelluser data, femtocell user data, and femtocell signaling. L-SGW 2101,L-PGW 2102, Ethernet system 2104, and LTE UE 405 exchange the femtocelldata over the F-SGi tunnels using the requisite QCI/DSCP QoS. L-SGW2101, L-PGW 2102, Ethernet system 2104, and LTE UE 405 exchange thefemtocell signaling over the femto signaling tunnel using the requisiteQCI/DSCP QoS.

L-SGW 2101 has a Children's Internet Protection Act (CIPA) filterapplication to filter user data. Macrocell PCRF 435 has a CIPA pitcherthat transfers CIPA filter flags and configuration data to L-PCRF 2103over the P-S15 links. L-PCRF 2103 transfers the CIPA filter flags andconfiguration data to the CIPA application in L-SGW 2101. L-SGW 2101filters the P-S1U user data using in the CIPA filter application asconfigured by macro PCRF 435.

FIG. 22 illustrates macrocell eNodeB 421 and S-GW 431. Macrocell eNodeB421 comprises LTE transceiver 2201 and S1 interface 2203. S-GW 431comprises S1 interface 2204, S5 interface 2205, and S11 interface 2206.LTE transceiver 2201 exposes LTE interfaces to UEs, femtocell relays,and picocell relays. LTE transceiver 2201 broadcasts LTE PLMN IDs forMACRO UE DATA, MACRO UE VOLTE, and MACRO RELAY.

For the typical UE, LTE transceiver 2201 exchanges its LTE signaling anduser data (M-S1-MME and M-S1U) with S1 interface 2203. For femtocell andpicocell relays, LTE transceiver 901 applies RoHCcompression/decompression to the user data that traverses F-SGi (2) andP-SGi (2) tunnels. LTE transceiver 2201 applies generalcompression/decompression to the femtocell and picocell signaling(F-S1-MME(2), F-S11(2), F-X2(2), F-Gz/Gy(2), F-S15(2), P-S1-MME(2),P-S11(2), P-X2(2), P-Gz/Gy(2), and P-S15(2)) exchanged over the LTEsignaling tunnels. LTE transceiver 2201 and S1 interface 2203 exchangethe femtocell and picocell signaling and user data.

S1 interface 2203 exchanges macro signaling (M-S1-MME) with MME 432. S1interface 2203 exchanges user data (M-S1U) with S1 interface 2204 ofS-GW 431. The M-S1U interface transports the femtocell and picocellsignaling and user data (F-S1-MME(2), F-S11(2), F-X2(2), F-Gz/Gy(2),F-S15(2), P-S1-MME(2), P-S11(2), P-X2(2), P-Gz/Gy(2), P-S15(2), F-S5(2),F-S2a(2), P-S5(2), and P-S2a(2)). S1 interface 2204 exchanges thefemtocell and picocell signaling and user data with S5 interface 2205.S5 interface 2205 exchanges user data (M-S5) with P-GW 434. The M-S5interface transports the femtocell and picocell signaling and user data.S11 interface 906 exchanges macro signaling (M-S11) with MME 432.

Macro eNodeB 421 and S-GW 431 apply LTE QoS to the bearers as indicatedby the specified QCIs. Macro eNodeB 421 and S-GW 431 exchange the LTEsignaling using QCI 5. Macro eNodeB 421 and S-GW 431 exchange the F-SGiuser data using QCI 1, QCI 5, QCI 9, or some other data QCI.

FIG. 23 illustrates macrocell P-GW 434 and R-GW 437. Macro S-GW 431 andSe-GW 438 are shown again for reference. Macrocell P-GW 434 comprises S5interface 2301 and SGi interface 2303. R-GW 437 comprises SGi interface2304, S1-MME interface 2305, S11 interface 2306, X2 interface 2307, S15interface 2308, and G interface 2309. Macrocell P-GW 434 exchanges itsM-Gx data with PCRF 435 and exchanges its M-Gz/Gy data with ACCT 436.

In P-GW 434, S5 interface 2301 exchanges the user data (F-SGi (1)(2) andP-SGi(1)(2)) with SGi interface 2303. SGi interface 2303 performsfunctions like routing and filtering on the user data for exchange withthe Internet, IMS, or some other system over the SGi links. S5 interface2301 exchanges LTE signaling (F-S1-MME(2), F-S11(2), F-X2(2),F-Gz/Gy(2), F-S15(2), P-S1-MME(2), P-S11(2), P-X2(2), P-Gz/Gy(2), andP-S15(2)) with SGi interface 2303. SGi interface 2303 exchanges the LTEsignaling with SGi interface 2304 in R-GW 437. In R-GW 437, SGiinterface 2304 also receives LTE signaling (F-S1-MME(1), F-S11(1),F-X2(1), F-Gz/Gy(1), F-S15(1), P-S1-MME(1), P-S11(2), P-X2(1),P-Gz/Gy(1), and P-S15(1)) from Se-GW 438. SGi interface 2304 performsfunctions like routing and filtering on the LTE signaling.

SGi interface 2304 exchanges the LTE signaling with proxy interfaces2305-2309, and proxy interfaces 2305-2309 exchange the LTE signalingwith various systems. Proxy interfaces 2305-2309 aggregate the LTEsignaling that was exchanged over the LAN/WAN backhaul and over theLWA/LTE backhaul. S1-MME interface 2305 exchanges the F-S1-MME andP-S1-MME signaling with MME 432. S11 interface 2306 exchanges F-S11 andP-S11 signaling with MME 432. X2 interface 2307 exchanges F-X2 and P-X2signaling with macrocell eNodeB 421. S15 interface 2308 exchanges F-S15and P-S15 signaling with PCRF 435. G interface 2309 exchanges F-Gz/Gyand P-Gz/Gy signaling with ACCT 436.

Macro P-GW 434 applies LTE QoS to the bearers as indicated by thespecified QCIs. Macro P-GW 434 exchanges the LTE signaling using QCI 5.P-GW 434 exchanges the user data using a QCI 1, QCI 5, QCI 9, or someother data QoS. R-GW 437 applies at least a QCI 5 type QoS to itssignaling data.

FIG. 24 illustrates UE 402 attachment to picocell 420 to use the P-SGidata bearer. The prior attachment of picocell relay 420 to macrocelleNodeB 421 to establish the P-SGi data bearer is like that shown in FIG.11 and is omitted for brevity. UE 402 responds to the SSIDs or PLMN IDsof PICO UE DATA and PICO UE VOLTE from picocell relay 420 (eNodeB 422)during an LWA attachment session using LTE or WiFi. UE 402 transfersinformation for MME 432 in a NAS message during LWA attachment. Inresponse to the UE 402 attachment, picocell relay 420 selects R-GW 437and transfers a Picocell (P) S1-MME initial UE message containing theNAS message to R-GW 437. The P-S1-MME message uses the signaling bearerthat traverses the LTE/S1-MME/S5/SGi interfaces of eNodeB 421, S-GW 431,and P-GW 434. The P-S1-MME initial UE message indicates the IP addressfor picocell relay 420. R-GW 437 transfers the P-S1-MME initial UEmessage to MME 432.

MME 432 authorizes UE 402 and retrieves UE APNs DATA and VOLTE from HSS433. In some examples, additional UE APNs are implemented like VIDEO.MME 432 responds to R-GW 437 with the UE APNs in a P-S11 create sessionrequest. R-GW 437 transfers the compressed P-S11 create session requestwith the UE 402 APNs to picocell relay 420 (L-SGW 2101) over thesignaling bearer that traverses the SGi/S5/S1U/LTE interfaces of P-GW434, S-GW 431, and eNodeB 421.

Responsive to the P-S11 create session request in picocell relay 420,L-SGW 2101 passes an internal P-S5 create session request to L-PGW 2102,and L-PGW 2102 selects IP addresses for UE 402. L-PGW 2102 may subnetone of its own IPv6 addresses or perform Network Address PortTranslation (NAPT) on one of its IPv4 addresses. L-PGW 2102 transfers aP-CCR to L-PCRF 2103. The P-CCR indicates the IP address and ID of UE402 and indicates the IP address of picocell relay 420. L-PCRF 2103 addsQCIs 1, 5, and 9 to serve the UE APN VOLTE and DATA over the picocellLWA access link. Picocell relay 420 (L-PCRF 2103) transfers the P-CCR toR-GW 437 over the signaling bearer that traverses the LTE/S1U/S5/SGiinterfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers theP-CCR to PCRF 435.

PCRF 435 returns a P-CCA to R-GW 437 which transfers the P-CCA topicocell relay 420 (L-PCRF 2103) over the signaling bearer thattraverses the SGi/S5/S1U/LTE interfaces of P-GW 434, S-GW 431, andeNodeB 421. The P-CCA indicates the QCI 1, QCI 5, and QCI 9 bearers forthe UE APNs over the LWA access link and the picocell data and signalingbearers. In picocell relay 420, L-PCRF 2103 transfers the P-CCA to L-PGW2002 which transfers a P-S5 create bearer request to L-SGW 2101. Inresponse to the P-S5 create bearer request, picocell relay 420 (L-SGW2001) transfers a P-S11 create session response to R-GW 437 over thesignaling bearer that traverses the LTE/S1U/S5/SGi interfaces of eNodeB421, S-GW 431, and P-GW 434. R-GW 437 transfers the P-S11 create sessionresponse to MME 432.

In response to the P-S11 create session response for the UE APNs andQCIs, MME 432 returns a P-S1-MME message to R-GW 437. The P-S1-MMEmessage has an initial context request and attach acceptance andindicates the IP addresses, APNs, and QCIs for UE 402. R-GW 437transfers the P-S1-MME message to picocell relay 420 (eNodeB 422) overthe signaling bearer that traverses the SGi/S5/S1U/LTE interfaces ofP-GW 434, S-GW 431, and eNodeB 421.

In response to the P-S1-MME message, UE 402 and picocell 420 (eNodeB422) perform an LWA attach acceptance session over LTE or WiFi thatdelivers the IP addresses, APNs, and QCIs for UE 402 to UE 402. Inresponse to the UE 402 attach acceptance, picocell relay 420 (eNodeB422) transfers a P-S1-MME initial context response and attach complete(OK) message to R-GW 437 over the signaling bearer that traverses theLTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW437 transfers the P-S1-MME initial context response and attach completeto MME 432.

In response to the P-S1-MME initial context response and attachcomplete, MME 432 transfers a P-S11 modify bearer request to R-GW 437.R-GW 437 transfers the P-S11 modify bearer request to picocell relay 420(L-SGW 2101) over the signaling bearer that traverses the SGi/S5/S1U/LTEinterfaces through P-GW 434, S-GW 431, and eNodeB 421. Responsive to theP-S11 modify bearer request, picocell relay 420 (L-SGW 2101) transfers aP-S11 modify bearer response to R-GW 437 over the signaling bearer thattraverses the LTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, andP-GW 434. R-GW 437 transfers the P-S11 modify bearer response to MME432.

Although not shown for clarity, UE 402 may exchange user data withpicocell relay 420 over LWA based on the specified APNs and QCIs.Picocell relay 420 may exchange the user data with P-GW 434 over theP-SGi data bearer that traverses the LTE/S1U/S5 interfaces of eNodeB 421and S-GW 431.

FIG. 25 illustrates femtocell relay 410 attachment to picocell relay 420to establish the femtocell F-SGi user data bearer and the femtocellsignaling bearer. Femtocell relay 410 also attaches to the LAN/WAN andSe-GW 437. These attachments could be standard and are not shown forclarity. Femtocell relay 410 responds to the SSIDs or PLMN IDs of PICORELAY from picocell relay 420 (eNodeB 422) during an LWA attachmentsession using LTE or WiFi. Femtocell relay 410 transfers information forMME 432 in a NAS message during LWA attachment. In response to femtocellrelay 410 attachment, picocell relay 420 selects R-GW 437 and transfersan P-S1-MME initial UE message containing the NAS message to R-GW 437.The P-S1-MME message uses the signaling bearer that traverses theLTE/S1-MME/S5/SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434. TheP-S1-MME initial UE message indicates the IP address for picocell relay420. R-GW 437 transfers the P-S1-MME initial UE message to MME 432.

MME 432 authorizes femtocell relay 410 and retrieves femtocell APNs forDATA and SIG from HSS 433. MME 432 responds to R-GW 437 with thefemtocell APNs in a P-S11 create session request. R-GW 437 transfers theP-S11 create session request with the femtocell APNs to picocell relay420 (L-SGW 2101) over the signaling bearer that traverses theSGi/S5/S1U/LTE interfaces of P-GW 434, S-GW 431, and eNodeB 421.

Responsive to the P-S11 create session message in picocell relay 420,L-SGW 2101 passes an internal P-S5 create session message to L-PGW 2102with the femtocell APNs. In response, L-PGW 2102 selects IP addressesfor femtocell relay 410. L-PGW 2102 may subnet one of its own IPv6addresses or NAPT one of its IPv4 addresses. L-PGW 2102 transfers aP-CCR to L-PCRF 2103 indicating the femtocell ID, IP addresses, andAPNs. L-PCRF 2003 adds QCIs 5 and 9 to service the femtocell APNs overthe picocell LWA access links. The P-CCR also indicates the IP addressof picocell relay 420. Picocell relay 420 (L-PCRF 2103) transfers theP-CCR to R-GW 437 over the signaling bearer that traverses theLTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, and P-GW 434. R-GW437 transfers the P-CCR to PCRF 435. PCRF 435 returns a P-CCA to R-GW437 that has QCI 9 for data bearer and QCI 5 for the signaling bearer.R-GW 437 transfers the P-CCA to picocell relay 420 (L-PCRF 2003) overthe signaling bearer that traverses the SGi/S5/S1U/LTE interfaces ofP-GW 434, S-GW 431, and eNodeB 421.

In picocell relay 420, L-PCRF 2103 transfers the P-CCA with thefemtocell QCIs to L-PGW 2102 which transfers a P-S5 create sessionresponse to L-SGW 2101. In response to the P-S5 create session response,picocell relay 420 (L-SGW 2101) transfers a P-S11 create sessionresponse for the femtocell APNs and QCIs to R-GW 437 over the signalingbearer that traverses the LTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the P-S11 create session responseto MME 432. In response to the P-S11 create session response for thefemtocell QCIs, MME 432 returns a P-S1-MME message to R-GW 437. TheP-S1-MME message has an initial context request and attach acceptanceand indicates the IP addresses, APNs, and QCIs for femtocell relay 410.R-GW 437 transfers the P-S1-MME message to picocell relay 420 (eNodeB422) over the signaling bearer that traverses the SGi/S5/S1U/LTEinterfaces of P-GW 434, S-GW 431, and eNodeB 421.

In response to the P-S1-MME message, femtocell relay 410 (UE 404) andpicocell 420 relay (eNodeB 422) perform an LWA attach acceptance sessionover LTE or WiFi that delivers the IP addresses, APNs, and QCIs forfemtocell relay 410 to relay 410. In response to the femtocell attachacceptance, picocell relay 420 (eNodeB 422) transfers a P-S1-MME initialcontext response and attach complete (OK) message to R-GW 437 over thesignaling bearer that traverses the LTE/S1U/S5/SGi interfaces of eNodeB421, S-GW 431, and P-GW 434. R-GW 437 transfers the P-S1-MME initialcontext response and attach complete to MME 432.

In response to the P-S1-MME initial context response and attachcomplete, MME 432 transfers a P-S11 modify bearer request to R-GW 437.R-GW 437 transfers the P-S11 modify bearer request to picocell relay 420(L-SGW 2101) over the signaling bearer that traverses the SGi/S5/S1U/LTEinterfaces through P-GW 434, S-GW 431, and eNodeB 421. Responsive to theP-S11 modify bearer request, picocell relay 420 (L-SGW 2101) transfers aP-S11 modify bearer response to R-GW 437 over the signaling bearer thattraverses the LTE/S1U/S5/SGi interfaces of eNodeB 421, S-GW 431, andP-GW 434. R-GW 437 transfers the P-S11 modify bearer response to MME432.

Although not shown for clarity, femtocell relay 410 may exchange userdata with picocell relay 420 over LWA based on the femtocell APNs andQCIs. Femtocell relay 410 may exchange user data with P-GW 434 over theF-SGi user data bearer that traverses the LWA/LTE/S1U/S5 interfaces ofpicocell relay 420, eNodeB 421 and S-GW 431. Femtocell relay 410 mayexchange LTE signaling with R-GW 437 over the signaling bearer thattraverses the LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420,eNodeB 421, S-GW 431, and P-GW.

FIG. 26 illustrates UE 403 attachment to femtocell 420 to use the F-SGiuser data bearer. UE 403 responds to the SSIDs or PLMN IDs of FEMTO UEDATA and FEMTO UE VOLTE from femtocell relay 410 (eNodeB 423) during anLWA attachment session using LTE or WiFi. UE 403 transfers informationfor MME 432 in a NAS message during LWA attachment. In response to theUE 402 attachment, femtocell relay 410 selects R-GW 437 and transfers anF-S1-MME initial UE message containing the NAS message to R-GW 437. TheF-S1-MME message uses the signaling bearer that traverses theLWA/LTE/S1-MME/S5/SGi interfaces of picocell 420, eNodeB 421, S-GW 431,and P-GW 434. The P-S1-MME initial UE message indicates the IP addressfor femtocell relay 410. R-GW 437 transfers the P-S1-MME initial UEmessage to MME 432.

MME 432 authorizes UE 403 and retrieves UE APNs like DATA and VOLTE fromHSS 433. In some examples, additional UE APNs are implemented likeVIDEO. MME 432 responds to R-GW 437 with the UE APNs in an F-S11 createsession request. R-GW 437 transfers the F-S11 create session requestwith the UE 403 APNs to femtocell relay 410 (L-SGW 2001) over thesignaling bearer that traverses the SGi/S5/S1U/LTE/LWA interfaces ofP-GW 434, S-GW 431, eNodeB 421, and picocell 420.

Responsive to the F-S11 create session message in femtocell relay 410,L-SGW 2001 passes an internal F-S5 create session message to L-PGW 2002with the UE APNs DATA and VOLTE. In response, L-PGW 2002 selects IPaddresses for UE 403. L-PGW 2002 may subnet one of its IPv6 addresses orNAPT on one of its IPv4 addresses. L-PGW 2002 transfers an F-CCR withthe UE ID and UE APNs to L-PCRF 2003. L-PCRF 2003 adds QCIs 9 and 5 toserve the UE APNs over the femtocell LWA access link. The F-CCR alsoindicates the IP address of femtocell relay 410. Femtocell relay 410(L-PCRF 2003) transfers the F-CCR to R-GW 437 over the signaling bearerthat traverses the LWA/LTE/S1U/S5/SGi interfaces of picocell relay 420,eNodeB 421, S-GW 431, and P-GW 434. R-GW 437 transfers the P-CCR to PCRF435.

PCRF 435 returns an F-CCA having the UE QCIs 5 and 9 to R-GW 437 whichproxies the F-CCA to femtocell relay 410 (L-PCRF 2003) over thesignaling bearer that traverses the SGi/S5/S1U/LTE/LWA interfaces ofP-GW 434, S-GW 431, eNodeB 421, and picocell relay 420. In femtocellrelay 410, L-PCRF 2003 transfers the F-CCA to L-PGW 2002 which transfersan F-S5 create session response to L-SGW 2001, In response to the F-S5create session response, femtocell relay 410 (L-SGW 2001) transfers anF-S11 create session response to R-GW 437 over the signaling bearer thattraverses the LWA/LTE/S1U/S5/SGi interfaces of picocell 420, eNodeB 421,S-GW 431, and P-GW 434. R-GW 437 transfers the F-S11 create sessionresponse to MME 432.

In response to the F-S11 create session response with the UE QCIs, MME432 returns an F-S1-MME message to R-GW 437. The F-S1-MME message has aninitial context request and attach acceptance and indicates the IPaddresses, APNs, and QCIs for UE 403. R-GW 437 transfers the F-S1-MMEmessage to femtocell relay 410 (eNodeB 423) over the signaling bearerthat traverses the SGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431,eNodeB 421, and picocell 420.

In response to the P-S1-MME message, UE 403 and femtocell relay 410(eNodeB 423) perform an LWA attach acceptance session over LTE or WiFithat delivers the IP addresses, APNs, and QCIs for UE 403 to UE 403. Inresponse to the UE 403 attach acceptance, femtocell relay 410 (eNodeB423) transfers an F-S1-MME initial context response and attach complete(OK) message to R-GW 437 over the signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell 420, eNodeB 421, S-GW 431, andP-GW 434. R-GW 437 transfers the F-S1-MME initial context response andattach complete to MME 432.

In response to the F-S1-MME initial context response and attachcomplete, MME 432 transfers an F-S11 modify bearer request to R-GW 437.R-GW 437 transfers the F-S11 modify bearer request to femtocell relay410 (L-SGW 2001) over the signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell 420. Responsive to the F-S11 modify bearer request, femtocellrelay 410 (L-SGW 2001) transfers an F-S11 modify bearer response to R-GW437 over the signaling bearer that traverses the LWA/LTE/S1U/S5/SGiinterfaces of picocell 420, eNodeB 421, S-GW 431, and P-GW 434. R-GW 437transfers the F-S11 modify bearer response to MME 432.

Although not shown for clarity, UE 403 may exchange user data withfemtocell relay 410 over LWA based on the specified APNs and QCIs.Femtocell relay 410 may exchange the user data with P-GW 434 over theF-SGi data bearer that traverses the LWA/LTE/S1U/S5 interfaces ofpicocell 420, eNodeB 421, and S-GW 431.

FIG. 27 illustrates Internet service from femtocell relay 420. UE 403transfers an LWA internet connection request to femtocell relay 410(eNodeB 423). In response to the LWA internet connection request,femtocell relay 410 transfers an F-S1-MME initial UE service requestcontaining a NAS message with the internet request to R-GW 437. TheF-S1-MME message uses the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S1-MME initial UE servicerequest to MME 432.

In response to the F-S1-MME initial UE service request with the internetrequest, MME 432 returns an F-S1-MME initial context request to R-GW437. R-GW 437 transfers the F-S1-MME initial context request tofemtocell relay 410 (eNodeB 423) over the femtocell signaling bearerthat traverses the SGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431,eNodeB 421, and picocell relay 420.

In response to the F-S1-MME initial context request, femtocell relay 410(eNodeB 423) returns an F-S1-MME initial context response to R-GW 437over the femtocell signaling bearer that traverses theLWA/LTE/S1U/S5/M-SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-S1-MME initial contextresponse to MME 432. In response to the F-S1-MME initial contextresponse, MME 432 transfers an F-S11 modify bearer request to R-GW 437.R-GW 437 proxies the F-S11 modify bearer request to femtocell relay 410(L-SGW 2001) over the femtocell signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420.

Responsive to the F-S11 modify bearer request in femtocell relay 410,L-SGW 2001 passes an internal F-S5 modify bearer request to L-PGW 2002,and L-PGW 2002 selects IP addresses for UE 403. L-PGW 2002 may subnetone of its own IPv6 addresses or NAPT one of its IPv4 addresses. L-PGW2002 transfers an F-CCR to L-PCRF 2003 with the UE APN DATA and the IPaddress of the signaling bearer for femtocell relay 410. L-PCRF 2003adds QCI 9 (or another QCI based on the service request) for thefemtocell LWA access link. Femtocell relay 410 (L-PCRF 2003) transfersthe F-CCR to R-GW 437 over the signaling bearer that traverses theLWA/LTE/S1U/S5/SGi interfaces of picocell relay 420, eNodeB 421, S-GW431, and P-GW 434. R-GW 437 transfers the F-CCR to PCRF 435.

PCRF 435 returns an F-CCA to R-GW 437 with QCI 9 for the F-SGi databearer for UE 403. R-GW 437 transfers the F-CCA to femtocell relay 410(L-PCRF 2003) over the signaling bearer that traverses theSGi/S5/S1U/LTE/LWA interfaces of P-GW 434, S-GW 431, eNodeB 421, andpicocell relay 420. In femtocell relay 410, L-PCRF 2003 transfers theF-CCA to L-PGW 2002 which transfers an F-S5 modify bearer response toL-SGW 2001, In response to the F-S5 modify bearer response, femtocellrelay 410 (L-SGW 2001) transfers an F-S11 modify bearer response to R-GW437 over the signaling bearer that traverses the LWA/LTE/S1U/S5/SGiinterfaces of picocell 420, eNodeB 421, S-GW 431, and P-GW 434. R-GW 437transfers the F-S11 modify bearer response to MME 432.

Although not shown for clarity, UE 403 may exchange user data withfemtocell relay 410 over LWA based on the specified DATA APN and QCI 9or some other QCI as requested. Femtocell relay 410 may exchange theuser data with P-GW 434 over the F-SGI data bearer that traverses theLWA/LTE/S1U/S5 interfaces of picocell 420, eNodeB 421, and S-GW 431.

FIG. 28 illustrates UE VoLTE service from femtocell relay 420 for UE403. Macro PCRF 435 receives an add VoLTE bearer request from IMS for UE403. In response to the VoLTE bearer request, macro PCRF 435 transfers aRe-Authorization Request (RAR) for VoLTE/QCI 1 to P-GW 434. In responseto the RAR, P-GW 434 transfers an M-S5 create bearer request for QCI 1to S-GW 431 which transfers an M-S11 create bearer request for QCI 1 toMME 432.

In response to the M-S11 create bearer request for QCI 1, MME 432transfers an M-S1-MME VoLTE create bearer/session management requestmacrocell eNodeB 421. In response to the M-S1-MME VoLTE bearerset-up/session management request, eNodeB 421 sends an LTE VoLTEreconfiguration request to picocell relay 420 (UE 405) and picocellrelay 420 (UE 405) reconfigures itself for QCI 1 on the F-SGi databearer and responds back to eNodeB 421. Macrocell eNodeB 421 transfersan M-S1-MME create bearer/session management response for VoLTE to MME432.

Also in response to the M-S11 create bearer request for VoLTE through apicocell, MME 432 transfers a P-S1-MME VoLTE create bearer/sessionmanagement request to picocell relay 420 (eNodeB 422) over the signalingbearer that traverses the SGi/S5/S1U/LTE/LWA interfaces of R-GW 437,P-GW 434, S-GW 431, and eNodeB 421. In response to the P-S1-MME VoLTEcreate bearer/session management request, picocell relay 420 (eNodeB422) sends a VoLTE LWA reconfiguration request to femtocell relay 410(UE 404) and femtocell relay 410 (UE 404) reconfigures itself for QCI 1on the F-SGi data bearer and responds back to picocell relay 420 (eNodeB422). In picocell relay 420, eNodeB 422 transfers a P-S1-MME createbearer/session management response for VoLTE to MME 432 over thesignaling bearer that traverses the LTE/S1U/S5/SGi interfaces ofpicocell relay 420, eNodeB 421, S-GW 431, P-GW 434, and R-GW 437.

In response to the M-S1-MME and the P-S1-MME create bearer/sessionmanagement responses for VoLTE, MME 432 transfers an M-S11 create bearerresponse for VoLTE to S-GW 431. S-GW 431 forwards an M-S5 create bearerresponse to P-GW 434, and P-GW 434 returns an M-RAA to PCRF 435.

In femtocell relay 410 responsive to the VoLTE reconfiguration, UE 404transfers a VoLTE F-RAR to L-PCRF 2003, and L-PCRF 2003 transfers theF-RAR to L-PGW 2002. In response, L-PGW 2002 transfers an F-S5 addbearer request to L-SGW 2001. In femtocell relay 410, L-SGW 2001responsively transfers an F-S11 add bearer request to MME 432 over thesignaling bearer that traverses the LWA/LTE/S1U/S5/SGi interfaces ofpicocell relay 420 eNodeB 421, S-GW 431, P-GW 434, and R-GW 437.

In response to the F-S11 create bearer request for the VoLTE, MME 432transfers an F-S1-MME bearer set-up/session management request for VoLTEto femtocell relay 410 (eNodeB 423). The F-S1-MME bearer set-up/sessionmanagement request traverses the SGi/S5/S1U/LTE/LWA interfaces of R-GW437, P-GW 434, S-GW 431, eNodeB 421, and picocell relay 420. In responseto the F-S1-MME bearer set-up/session management request for the VoLTE,femtocell relay 410 (eNodeB 423) reconfigures itself and UE 403 for QCI1 over the LWA access link. Femtocell relay 410 (eNodeB 423) transfersan F-S1-MME bearer set-up/session management response to MME 432 overthe signaling bearer that traverses the LWA/LTE/S1U/S5/SGi interfaces ofpicocell relay 420, eNodeB 421, S-GW 431, P-GW 434, and R-GW 437.

In response to the F-S1-MME bearer set-up/session management response,MME 432 transfers an F-S11 create bearer response to femtocell relay 410over the SGi/S5/S1U/LTE/LWA interfaces of R-GW 437, P-GW 434, S-GW 431,eNodeB 421, and picocell relay 410. In femtocell relay 410, L-SGW 2001responsively transfers an F-S5 create bearer response to L-PGW 2002, andL-PGW 2002 transfers an F-RAA to L-PCRF 2003.

UE 403 may now exchange user voice with femtocell relay 410 over LTE orWiFi based on QCI 1. Femtocell relay 410 and the P-GW 434 exchange theuser voice over the QCI 1 F-SGi data bearer. P-GW 434 performsformatting and filtering on the user voice data and exchanges the uservoice data with external systems.

The above description and associated figures teach the best mode of theinvention. The following claims specify the scope of the invention. Notethat some aspects of the best mode may not fall within the scope of theinvention as specified by the claims. Those skilled in the art willappreciate that the features described above can be combined in variousways to form multiple variations of the invention. As a result, theinvention is not limited to the specific embodiments described above,but only by the following claims and their equivalents.

What is claimed is:
 1. A method of operating a wireless relay to controlbackhaul in a data communication network, the method comprising: relayuser equipment wirelessly attaching to a wireless base station coupledto a data network core and receiving a first backhaul connection from arelay base station through the wireless base station to the data networkcore; an Ethernet switch attaching to a network gateway coupled to thedata network core and establishing a second backhaul connection from therelay base station through the network gateway to the data network core;the relay base station receiving status data for the first backhaulconnection through the wireless base station; and the relay base stationexchanging wireless user data with served user equipment, selecting oneof the backhaul connections for the user data based on the status dataof the first backhaul connection through the wireless base station, andexchanging the user data with the data network core over the selectedone of the backhaul connections.
 2. The method of claim 1 furthercomprising the relay base station establishing at least one signalinglink over at least one of the backhaul connections and wherein receivingthe status data for the first backhaul connection comprises receivingthe status data over the signaling link.
 3. The method of claim 2wherein the signaling link comprises an X2 link to the macrocell basestation.
 4. The method of claim 2 wherein the signaling link comprisesan S1-MME link to a Mobility Management Entity (MME) in the data networkcore.
 5. The method of claim 1 wherein: the relay base stationexchanging the wireless user data with the served user equipmentcomprises the relay base station exchanging a media type with the serveduser equipment; and the relay base station selecting one of the backhaulconnections for the user data comprises selecting the first backhaulconnection based on the exchange of the media type and the status datafor the first backhaul connection.
 6. The method of claim 5 wherein themedia type comprises voice data.
 7. The method of claim 6 furthercomprising the relay user equipment compressing and decompressing thevoice data exchanged over the first backhaul connection.
 8. The methodof claim 1 wherein: the relay base station exchanging the wireless userdata with the served user equipment comprises the relay base stationexchanging generic internet traffic with the served user equipment; andthe relay base station selecting one of the backhaul connections for theuser data comprises selecting the second backhaul connection based onthe exchange of generic internet traffic and the status data for thefirst backhaul connection.
 9. The method of claim 1 wherein: the relaybase station receiving status data for the second backhaul connectionthrough the network gateway; and the relay base station exchanging thewireless user data with the served user equipment comprises the relaybase station exchanging generic internet traffic with the served userequipment; and the relay base station selecting one of the backhaulconnections for the user data comprises selecting the second backhaulconnection based on the exchange of generic internet traffic and thestatus data for the second backhaul connection.
 10. The method of claim1 wherein: the relay base station receiving status data for the secondbackhaul connection through the network gateway; and the relay basestation exchanging the wireless user data with the served user equipmentcomprises the relay base station exchanging a media type with the serveduser equipment; and the relay base station selecting one of the backhaulconnections for the user data comprises selecting one of the backhaulconnections based on the exchange of the media type and the status datafor the first backhaul connection and the status data for the secondbackhaul connection.
 11. A wireless relay to control backhaul in a datacommunication network, the wireless relay comprising: relay userequipment configured to wirelessly attach to a wireless base stationcoupled to a data network core and receive a first backhaul connectionfrom a relay base station through the wireless base station to the datanetwork core; an Ethernet switch configured to attach to a networkgateway coupled to the data network core and establish a second backhaulconnection from the relay base station through the network gateway tothe data network core; the relay base station configured to receivestatus data for the first backhaul connection through the wireless basestation; and the relay base station configured to exchange wireless userdata with served user equipment, select one of the backhaul connectionsfor the user data based on the status data of the first backhaulconnection through the wireless base station, and exchange the user datawith the data network core over the selected one of the backhaulconnections.
 12. The wireless relay of claim 11 wherein the relay basestation is configured to establish at least one signaling link over atleast one of the backhaul connections and to receive the status dataover the signaling link.
 13. The wireless relay of claim 12 wherein thesignaling link comprises an X2 link to the macrocell base station. 14.The wireless relay of claim 12 wherein the signaling link comprises anS1-MME link to a Mobility Management Entity (MME) in the data networkcore.
 15. The wireless relay of claim 11 wherein the wireless user datacomprises a media type and the relay base station is configured toselect the first backhaul connection based on the user data being themedia type and based on the status data for the first backhaulconnection.
 16. The wireless relay of claim 15 wherein the media typecomprises voice data.
 17. The wireless relay of claim 16 wherein therelay user equipment is configured to compress and decompress the voicedata exchanged over the first backhaul connection.
 18. The wirelessrelay of claim 11 wherein the wireless user data comprises genericinternet traffic and the relay base station is configured to select thesecond backhaul connection based on the user data being generic internettraffic and based on the status data for the first backhaul connection.19. The wireless relay of claim 11 wherein the wireless user datacomprises generic internet traffic and the relay base station isconfigured to receive status data for the second backhaul connectionthrough the network gateway and to select the second backhaul connectionbased on the user data being generic internet traffic and based on thestatus data for the second backhaul connection.
 20. The wireless relayof claim 11 wherein the wireless user data comprises a media type andthe relay base station is configured to receive status data for thesecond backhaul connection through the network gateway and select one ofthe backhaul connections for the user data based on the user data beingthe media type, based on the status data for the first backhaulconnection, and based on the status data for the second backhaulconnection.